Recent content by rawintellect

You have to change more than just your drive letter. Please see post number 45 in this thread for more information.

I noticed this too. When I do a scanhealth it gets corrupted again but checkhealth is fine as long as you don't do a scanhealth before it. So for now I just did the restorehealth then stayed away from scanhealth as checkhealth still reports all is well. So for now scanhealth is off the table for me.

I use "WhoCrashed." It will read the logs and tell you what caused it.

There are some things you'd need to change based upon (1) What drive you have the ISO mounted on and (2) Whether you are using ESD or WIM for compression. (3) The index number of your version of windows. Basically everything in red below needs changed depending upon what is on the ISO you're...

Nope.

I had the same issue with DISM /RESTOREHEALTH. I created the ISO from UUP, mounted it and issued this command and all was well. SFC was clean. dism /online /cleanup-image /restorehealth /Source:WIM:G:\sources\Install.wim:1 /limitaccess

Installed fine. DISM/SFC were good.

Frustrated with the restore option missing from WinRE? This fixed it for me! ;-) 1. Download or Mount the Windows ISO Go to the Microsoft Software Download site or UUPDUMP and download an ISO for your exact Windows version (Windows 10 or Windows 11). Once downloaded, right-click the ISO...

Are you using the UUP ISO to do this?

After running the logs through ChatGPT it concluded what I already knew: It's a bad ISO from UUP. It seems to be a mixture of 26100 binaries with 26200 ones. The earlier ISOs work fine as does the official Microsoft ISO. All we can do is wait for someone to notice it I guess.

Installed fine through windows update. I'm creating the ISO to test WinRE now.

I ran the install again just now to obtain the latest setupdiag.exe data. As you can see the only error message is the finalized last operation which was the removal of the PITR points. But then later in the log it says that operation completed successfully (true). All of this occurs before the...

I've done all of this. This isn't my first time with this error. It is the first time in a long while however. It's not a driver issue (at least any of my drivers I have installed). It's a WinRe (driver) issue. Which is why I tried all the versions leading up to 26200.8728 and they worked fine...

I use Intelligent Standby List Cleaner to purge my standby list. It works great!

Ah ha!!! It started with 26200.8728 and continued into 26200.8737.