Windows 10 update problem; "we can't tell if your pc is ready to continue installing windows 10"

[smithdog26]

both drives reporting as good

 

[Maxstar]

2022-12-27 19:14:21, Error                 SP     CApplyWIM: Failure while applying image 6 for C:\$WINDOWS.~BT\Sources\Install.esd. Error 0x8007025D[gle=0x0000025d]
2022-12-27 19:14:22, Error                 SP     Operation failed: Apply WIM file PathForNewOSFile (compact), index 6 to C:\$WINDOWS.~BT\NewOS. Error: 0x8007025D[gle=0x000000b7]

Both HDD's looking good, a faulty hard drive can be ruled out as the cause of the COMPRESSION_BUFFER error.

But 0x8007025D indicates there is some kind of issue with the (Windows Image) *.ESD file.

Use

Disk Cleanup to remove the C:\$WINDOWS.~BT\ directory.

• Click the Start button and in the search box, type cleanmgr to open Disk Cleanup.
• Select the systemdrive (usually C:\) and click OK.
• Now click on the Clean up system files button.
• Uncheck all the options and be sure only the following option is checked!
  • Temporary Windows installation files
• Click OK.
• Now disk cleanup will remove the C:\$WINDOWS.~BT\ directoy.

Let me know if it was succesful or not.

 

[smithdog26]

this successfully removed the C:\$WINDOWS.~BT\ directoy

 

[Maxstar]

Please download a new ISO using the Media Creation Tool and perform an in-place-upgrade again and let me know the result.

• Go to this Microsoft page and under the title Create Windows 10 installation media press on Download tool now.
• Save the tool on your Desktop and double click to run it.
• On the License terms page, if you accept the license terms, select Accept.
• On the What do you want to do page, select Create installation media (USB....) and then select Next.
• Choose the ISO file option. Once the download is complete, right click the ISO and select the option Mount.
• Open the Windows File Explorer and open mounted ISO, and run the setup.exe file.
• Follow the instructions and click on the option Change what to keep.
• Select the option Keep personal files and apps and click next.
• Windows Setup will now start the in-place upgrade installation to repair Windows.

 

[smithdog26]

The update failed again unfortunately. Same error codes as before.

 

[Maxstar]

Hi,

Please provide the following logs again.

Setupact.log and Setuperr.log from the following path C:\$Windows.~BT\Sources\Panther
And the log setupapi.dev.log from the following path C:\$Windows.~bt\Sources\Rollback\setupapi if exists.

 

[smithdog26]

Logs are all below. setupapi doesnt exist but I found a log called "setupapi.offline.log" in this directory C:\$WINDOWS.~BT\Sources\Rollback\WinPE\setupapi so I've attached that as well. There's a screenshot of the rollback directory for you as well.

 

[Maxstar]

Still the same issues, in this stage I think it might be worth to consider to backup all the the important data and perform a clean installation. Especially due to the number of issues with drivers which refer to D:\ - the (messed up) GPT partition table and the out-dated build of Windows 10.

To be honest, I've seen cases with the same error (0x8007025D - 0x2000C) during the installation of Windows, removing all of the existing partitions was the only solution to resolve the issue....

 

[smithdog26]

So I've managed to make a bit of progress with this, I decided to try and update to the next build after the one I was stuck in, 1703 -> 1709, and it worked. I had also disconnected my second HDD, optical disk drive and gone down to one dimm of ram while doing the updates.

I've been doing the updates one at a time in the order that they were released and all have been successful so far, currently I'm on version 1809, build 17763.107.

Hope this success continues, I'll let you know if it manages all the way to the latest release.

 

[Maxstar]

Hi,

That's interesting, then possibly the second hard drive is the culprit in here?!

 

[smithdog26]

Possibly, my thinking was that since the driver issue was pointing to D: then I could try and disconnect it since it's purely for file storage. Also because the version of windows was quite old I thought that updating a version at a time might help as well.

So I have made it up to the last build of version 1809 but the attempt to update to the 1903 version failed last night at 75%. I'll give it another go tonight and if it fails again I'll upload the logs here for you to have a look at.

 

[smithdog26]

Hi,

So its failing to update from 1809 to 1903, it makes it to 75% then at the restart goes straight to "attempting to recover install" followed by "undoing changes made to your computer".
I've tried through windows update and with the iso file, both with the same result.
sfc /scannow and DISM /online /cleanup-image /RestoreHealth have been run successfully.
I have noticed that there are now two recovery partitions showing in disk manager, reading about it the second larger one was probably created when i went from 1709 to 1803. I'm not sure if this is causing any issues though.
Below are the logs I thought might be useful.

 

[Maxstar]

Hi,

This time the upgrade failed with another error 0xc1900101 - 0x40017, this kind of secondary boot problems are quite common when the installation cannot set up the boot due to interference from something else. Which peripheral devices where connected to the system while upgrading?

 

[smithdog26]

No peripherals were attached, I still have the second HDD disconnected, ethernet was unplugged and even the keyboard and mouse were disconnected.

 

[Maxstar]

2023-01-07 15:14:13, Error      [0x0803b6] MIG    Can't retrieve group information for user IIS APPPOOL\DefaultAppPool. NetUserGetLocalGroups failed 0x000008AD

Okay, could you please uninstall Microsoft ASP.NET MVC 4 Runtime this application seems to be the cause of the error above. Afterwards reboot the system and try to upgrade again.

 

[smithdog26]

Okay I'll give that a try, thanks.

 

[Maxstar]

Good luck, the exact cause it's a little bit unclear due to the number of errors and other issues that might be the cause of the rollback.

 

[smithdog26]

failed again unfortunately. the logs are attached.

 

[Maxstar]

Please attach a screenshot of the following folder: C:\Windows\ServiceProfiles

 

[smithdog26]

of course