Recent content by fg2001gf11F

This is weird, it had already done a successful /RESTOREHEALTH after the update, and today it found repairable again on /SCANHEALTH and had to do another /RESTOREHEALTH, then /SCANHEALTH still found repairable. 😵‍💫🤷‍♂️ I tried 2 more times with the same result. 🤬🤷‍♂️

When did they add the 26H2 on that page? Another A/B testing? Typical Microsoft inconsistency and confusion. 🤬🤷‍♂️ I don't have that 26H2 Advanced Option on any of my machines with Build 26300.8772. 😵‍💫🤷‍♂️ Other users show that it accepted "Future Platform" even for 26H2.

Build 26300.8772 is a 26H2 Version, why is the insider page settings > Advance Options still shows 25H2. I think they need to add an option for 26H2. 😵‍💫🤷‍♂️ Edition Windows 11 Pro Insider Preview Version 26H2 Installed on ‎7/‎6/‎2026 Evaluation expires on ‎8/‎11/‎2026 11:09 AM OS...

I usually split the install.wim or install.esd to fit in the FAT32 formatted USB media. I let MCT create the ISO with the full install.esd, then I create a new ISO with install.swm, install2.swm and install3.swm if necessary that can be used to create the FAT32 installation media, see samples...

That is normal with insider ISO files. The install.esd is only created when you use MCT. 🤷‍♂️

Still broken boot.wim. Same problem with Official Microsoft ISO 28120.2387. When I hit "Repair my PC" it reboots to the main OS instead of to recovery. This problem is common to all recent official Microsoft insider ISO files. 🤬🤷‍♂️ https://aka.ms/AA11rcvu

This annoying notification is also happening with this Build 28120.2387.with Windows Security Service Version: 10.0.29573.1002-0.

This problem showed up today on Build 26300.8772. 😵‍💫🤷‍♂️ The security Application version was updated to 1000.29573.0.1002. Build 28120.2387 is also having this problem like 26300.8772. Note that another machine with the same build 26300.8772 still has 1000.29554.0.1001 and does not have this...

A user suggested to run these 2 commands first and then try /RESTOREHEALTH again. All my machines are now free from that error 0x800f0915. 🤷‍♂️ DISM /ONLINE /CLEANUP-IMAGE /ANALYZECOMPONENTSTORE DISM /ONLINE /CLEANUP-IMAGE /STARTCOMPONENTCLEANUP

Still clean /SCANHEALTH on 7/7/2026, 9:42 AM. 🤞

It did the same here with 26220.8764 on one machine, I ran /RESTOREHEALTH after a clean /SCANHEALTH and it failed one time, then ran again /RESTOREHEALTH later and it completed successfully. 😵‍💫🤷‍♂️ Who knows what happened at Microsoft with this long 4th of July weekend. 😵‍💫🤣🤷‍♂️

Looks like Microsoft may have changed something on their servers, because all the /RESTREHEALTH runs that failed earlier completed successfully a few hours later on the same machines. 😵‍💫🤷‍♂️

This one took a long time but eventually completed the /RESTOREHEALTH successfully without the error 0x800f0815. 🤞🤷‍♂️ Maybe Microsoft changed something in the last few hours. 😵‍💫 Same on these other 2 machines that were failing earlier with error: 0x800f0815. 👍 Looks like Microsoft changed...

What about build 26300.8772?

This is not Future Platforms is supposed to be 26H2. But the insider page still shows 25H2. 😵‍💫🤷‍♂️ Edition Windows 11 Pro Insider Preview Version 26H2 Installed on ‎5/‎8/‎2026 Evaluation expires on ‎8/‎11/‎2026 11:09 AM OS build 26300.8772 Experience Windows Feature...