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

[smithdog26]

files are below. There was no setupapi folder in the rollback folder (please see screenshot below).

 

[Maxstar]

2022-12-26 17:55:51, Error                 CONX   Windows::Compat::Appraiser::Utilities::GetWufbProperties (5750):   Error getting ReleaseEnterprisePolicyValue, swallowing: [127].[gle=0x8007007f]
2022-12-26 17:56:01, Error                 CONX   0xd0000034 Failed to add user mode driver [%SystemRoot%\system32\DRIVERS\UMDF\uicciso.dll]

Could you please provide a copy of the DRIVERS hive and and a new copy of COMPONENTS hive.

Upload your DRIVERS Hive

• Navigate to C:\Windows\System32\config and locate the DRIVERS file.
• Please copy this file to your desktop.
• Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
• Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named DRIVERS.ZIP on your desktop.
• If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

Upload your COMPONENTS hive.

• Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
• Please copy this file to your desktop.
• Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
• Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
• If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

 

[smithdog26]

copies attached

 

[Maxstar]

Hi,

Let's perform a filescan with SFCFix to get some more information.

Download

SFCFix and save it to your desktop.
Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFixScript.txt and save it to your desktop.
• Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

 

[smithdog26]

Log file below.

 

[Maxstar]

Please run the following command to export a registry key.

• Click the Start button and in the search box, type Command Prompt
• When you see Command Prompt on the list, right-click on it and select Run as administrator.
• Copy and paste the following command line and press Enter.

reg query "HKLM\SYSTEM\MountedDevices" /s > "%userprofile%\desktop\regexp.txt"

• When finished, a logfile called regexp.txt is saved on your desktop.
• Post the logfile as attachment in your next reply.

 

[Maxstar]

Perform the same steps as above with the following command to export another key.

reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WUDF" /s > "%userprofile%\desktop\regexp2.txt"

 

[smithdog26]

here are both exported reg files

 

[Maxstar]

Hi,

Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFix.zip and save it to your desktop.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Reboot the system and attempt to update, and let me know the result.

 

[smithdog26]

Here the log from sfcfix. I'll now attempt to update.

 

[smithdog26]

Update failed again. Internet was disconnected. I didn't see what point it failed at.

It was the exact same error codes that came up before.

 

[Maxstar]

Hi,

Could you please provide the logs again Setupact.log and Setuperr.log from the following path C:\$Windows.~BT\Sources\Panther.

 

[smithdog26]

logs attached

 

[Maxstar]

In the latest logs I've noticed several issues with drivers. here's an example of one of them:

2022-12-27 19:21:34, Error                 DISM   DISM Driver Manager: PID=2524 TID=2276 Failed opening driver package for x86: INF Name='C:\Windows\System32\DriverStore\FileRepository\vx6000m.inf_amd64_aba24d135649d103\vx6000m.inf' - CDriverPackage::OpenDmiDriverPackages(hr:0xe0000100)
2022-12-27 19:21:34, Error                 DISM   DISM Driver Manager: PID=2524 TID=2276 onecore\base\ntsetup\opktools\dism\providers\dmiprovider\dll\driverpackage.cpp:206 - CDriverPackage::Initialize(hr:0xe0000100)
2022-12-27 19:21:34, Error                 DISM   DISM Driver Manager: PID=2524 TID=2276 Failed to initialize the instance of CDriverPackage. - CDriverPackage::Create(hr:0xe0000100)
2022-12-27 19:21:34, Error                 DISM   DISM Driver Manager: PID=2524 TID=2276 Failed to create a driver package ATL object. - CDmiApi::DriverPackageOpenW(hr:0xe0000100)
2022-12-27 19:21:34, Error                 DISM   DISM Driver Manager: PID=2524 TID=2276 Failed to open a driver package object. - EnumDriverPackageRoutine(hr:0xe0000100)
2022-12-27 19:21:34, Info                  DISM   DISM Driver Manager: PID=2524 TID=2276 Could not add a driver into the driver enumeration list.  This driver may be corrupt: C:\Windows\System32\DriverStore\FileRepository\vx6000m.inf_amd64_aba24d135649d103\vx6000m.inf - EnumDriverPackageRoutine

Looking at the DRIVERS hive you provided in a previous post this driver is refering to D:\

[HKEY_LOCAL_MACHINE\DriversHsmithdog26\DriverDatabase\DriverPackages\vx6000m.inf_amd64_aba24d135649d103]
"Version"=hex:00,ff,09,00,00,00,00,00,6c,e9,36,4d,25,e3,ce,11,bf,c1,08,00,2b,\
  e1,03,18,00,c0,73,2d,d1,97,ca,01,00,00,72,17,03,00,06,00,00,00,00,00,00,00,\
  00,00
"Provider"="Microsoft"
"InfName"="vx6000m.inf"
"OemPath"="D:\\Windows\\System32\\DriverStore\\FileRepository\\vx6000m.inf_amd64_aba24d135649d103"
"SignerName"="Microsoft Windows Hardware Compatibility Publisher"
"ImportDate"=hex:f0,1f,e4,72,5b,eb,d2,01
"SignerScore"=dword:0d000005
"StatusFlags"=dword:00000100
@="oem100.inf"

Open an elevated command prompt and run the following command. Attach Dirlist.txt to your next post.

dir /s /a %systemroot%\System32\DriverStore\FileRepository\vx6000m.inf_amd64_aba24d135649d103 > "%userprofile%\Desktop\Dirlist.txt"

 

[smithdog26]

okay, well drive D: is just a secondary HDD I use for program file storage.

 

[Maxstar]

Things must have gone wrong while converting this disk from MBR to GPT?!

- The Windows Recovery partition was badly damaged or actually wrecked?
- The EFI was not in shape how it should be.
- Partition N:\ ? (I have no idea how it was created, but it must be related to the converting process)

Could you please provide a new copy of the DRIVERS hive.

Upload your DRIVERS Hive

• Navigate to C:\Windows\System32\config and locate the DRIVERS file.
• Please copy this file to your desktop.
• Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
• Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named DRIVERS.ZIP on your desktop.
• If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

 

[smithdog26]

yeah of course.

 

[Maxstar]

Please run the following command in an elevated command prompt as well, and attach "Drivers.txt" to your next post.

DISM /online /get-drivers /format:table > "%USERPROFILE%\desktop\Drivers.txt"

 

[smithdog26]

file below

 

[Maxstar]

Hi,

Let's check the system drive's first, just to be sure they are in a good condition.

Download

Crystal DiskInfo and save it to your Desktop.

• Run the installer to install the program.
• When finished, open the installed program by double clicking on it.
  • Good - There are no problems found, the drive is working properly.
  • Caution - The drive have some problems. (which indicates a drive that you should most likely be thinking about backing up and replacing.)
  • Bad - This usually indicates a drive that’s dead or near death. (! - Back up all important data as soon as possible.)
• Resize the window so that all information is visible.
• Take a screenshot of what you see and post it in your next reply.