Upgrade to Windows 10 fails

[SteveDG]

File attached.

 

[PeterJ]

Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

1. Download the attachment fixlist.txt and save it to your desktop.
2. Right-click on FRST64.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Attach the logfile Fixlog.txt to your next reply.

 

[SteveDG]

File attached.

Some of the entries show as "not found" because I removed them after the registry search yesterday.

 

[PeterJ]

Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

1. Download the attachment fixlist.txt and save it to your desktop.
2. Right-click on FRST64.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Attach the logfile Fixlog.txt to your next reply.

Step 2:
Restart the machine.
Try the upgrade again and report the result.

 

[SteveDG]

For some reason I can't see my replies from last Saturday on here anymore. I ran the fix, retried the update and it failed again at the usual place.

I've attached the fixlog and install logs again.

Also the Compatdata file reports multiple files as BlockMigration=True. Using pnputil I removed all apart from oem8, oem58 & oem141 and also removed the entries from the registry manually, retried the install but it failed in the usual spot again.

 

[PeterJ]

Please do following only.

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attachment SFCFixScript.txt and save it on your desktop.
• Save any work you have open, and close all programs.
• 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.
• Open the file, then copy and paste its content in your next reply.

 

[SteveDG]

SFCFix version 3.0.2.1 by niemiro.
Start time: 2023-11-04 18:33:41.647
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\Steve\Downloads\SFCFixScript.txt [0]




FileScan::
[0: 2] C:\Windows\winsxs\amd64_microsoft-windows-unbcl_31bf3856ad364e35_6.1.7600.16385_none_b80a18fcc5fabb4f\unbcl.dll
Expected: RSJqoTTFLcLsDA9qgMYGPMo3NWV7bVgrxbrKHRw7Zpk=
Expected: 6.1.7600.16385
Successfully traced component amd64_microsoft-windows-unbcl_31bf3856ad364e35_6.1.7600.16385_none_b80a18fcc5fabb4f.
Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery

[C:\Windows\System32\migwiz\unbcl.dll]


[1: 2] C:\Windows\winsxs\amd64_microsoft-windows-setup-component_31bf3856ad364e35_6.1.7601.17514_none_905283bdc3e1d2d8\unbcl.dll
Expected: 3ZKQ6p3o7el4HaZWFp0ZqYZon7/Vs7s0GuwWwnqWtw8=
Expected: 6.1.7601.17514 Found: 6.1.7600.16385
Successfully traced component amd64_microsoft-windows-setup-component_31bf3856ad364e35_6.1.7601.17514_none_905283bdc3e1d2d8.
Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery

[C:\Windows\System32\oobe\unbcl.dll]


[2: 2] C:\Windows\winsxs\x86_microsoft-windows-unbcl_31bf3856ad364e35_6.1.7600.16385_none_5beb7d790d9d4a19\unbcl.dll
Expected: KVH3oqnCrDkKTkW/MC6klGrT1Q4l+pGWuF8cQ4qPv+0=
Expected: 6.1.7600.16385
Successfully traced component x86_microsoft-windows-unbcl_31bf3856ad364e35_6.1.7600.16385_none_5beb7d790d9d4a19.
Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery

[C:\Windows\SysWOW64\migwiz\unbcl.dll]


[3: 2] C:\$WINDOWS.~BT\Sources\unbcl.dll
File is untraceable.
Found: jWtscHI4La3uDCbVQRcUIR1Tqi6Xrbmi5k3NQJc0W7M=
Found: 10.0.19041.2780
Trace not available.

[C:\Windows\System32\oobe\SetupPlatform\UNBCL.DLL]


[4: 1] C:\ESD\Windows\sources\unbcl.dll
File is untraceable.
Found: jWtscHI4La3uDCbVQRcUIR1Tqi6Xrbmi5k3NQJc0W7M=
Found: 10.0.19041.2780
Trace not available.



[5: 1] C:\FRST\Quarantine\C\Windows\System32\OOBE\SetupPlatform\UNBCL.DLL
File is untraceable.
Found: jWtscHI4La3uDCbVQRcUIR1Tqi6Xrbmi5k3NQJc0W7M=
Found: 10.0.19041.2780
Trace not available.
FileScan:: directive completed successfully.




Delete::
Successfully deleted files matching pattern C:\Windows\System32\OOBE\SetupPlatform.
Delete:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 5 datablocks.
Finish time: 2023-11-04 18:33:47.159
Script hash: C0IEn8XtNSq1QxO6a+LyiykujnUG0K7xzVk84pUXKDI=
----------------------EOF-----------------------

 

[PeterJ]

Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

1. Download the attachment fixlist.txt and save it to your desktop.
2. Right-click on FRST64.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Attach the logfile Fixlog.txt to your next reply.

 

[SteveDG]

File attached.

 

[PeterJ]

Try the upgrade again and report the result.

 

[SteveDG]

Upgrade failed (BSOD) at the 10% done mark of the working on updates phase. Stop code was MEMORY MANAGEMENT.

 

[PeterJ]

The upgrade always fails at the same spot for some reason.
Tell me the actions you did on the last upgrade attempt.

 

[SteveDG]

Recently it always fails with a BSOD at around the 9% - 13% done on the "working on updates" phase. The BSOD stop code is usually "IRQL NOT LESS OR EQUAL" or "MEMORY MANAGEMENT".

To run the update I disconnect all external devices except internet, mouse & keyboard, I restart the PC, log in (each of my family have a login - mine is set as administrator) and then run the update by right-clicking on the MediaCreationTool22H2 icon on the desktop and selecting "Run as Administrator". I then follow the prompts i.e. select Upgrade this PC, accept licence agreement, click OK to install Win 10 Pro and keep files and settings, etc. The install reboots the PC once during the process prior to the installing Win 10 phase. Each update attempt takes around 90 minutes with most of that time taken up by the Win 10 download. During the update there are two checks for updates and also two checks to make sure the PC is ready to update - none of these produces any messages. All seems normal until the BSOD appears.

After the rollback to Win 7 I recall that the BSOD initially didn't appear until around 84% done in the "working on updates" phase.

After the initial successful install/registration of Win 10 (1703) and the subsequent rollback due to problems with Avast, the rollback resulted in a number of permission issues and settings changes i.e.
. All files had the lock symbol next to them in file explorer and some people could no longer open files that they could previously open. Even my admin login couldn't open some files but I could reset permission levels to default or add user Everyone which resolved the issue.
. Even though the default browser was set to Microsoft Edge, attempts to open url's resulted in a message to select a browser being displayed. Setting the default browser to Edge again (even though it was already set to Edge) resolved this issue.
. There were similar issues with other default apps already being set but which Windows was apparently ignoring until I "set" them again.
. Plus some other issues I can't recall at present.

Over time I have tried upgrading:
. from DVD, USB and using the Media Creation Tool for 22H2 from the desktop.
. without first rebooting the PC,
. without selecting "Run as Administrator".
. doing a disk & system files cleanup from the C:\ properties window by selecting all files before the upgrade,
. without disconnecting external devices.
. using Win 10 versions 1703, 21H2 & 22H2.
. after disconnecting the internet but the upgrade failed immediately as it couldn't find the internet to download Win 10.

 

[PeterJ]

Hmm, that is al lot already done and tried.

Provide the System Hive

1. Start the program Regedit.exe.
2. In the left pane of Regedit browse to the key Computer\HKEY_LOCAL_MACHINE\SYSTEM
3. Right-click on it and select “Export”.
4. Choose as file location your desktop.
5. Typ for the file name "SYSTEM" and choose as type “Registry Hive Files (*.*)”.
6. Click the button Save.
7. When completed you can close Regedit.
8. Attach the file SYSTEM which should be now on your desktop to your next reply.

 

[SteveDG]

File was 55Mb so compressed (almost 10Mb) file attached.

 

[PeterJ]

The file is corrupt,7Zip says its empty, WinRar can open it but not extract the content.
Please check the zip file locally. If okay, upload the file again. If not create a new zip file first.

 

[SteveDG]

File extracts OK at this end but created new compressed file anyway.

 

[PeterJ]

Thanks. The latest attachment worked.

Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

1. Download the attachment fixlist.txt and save it to your desktop.
2. Right-click on FRST64.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Attach the logfile Fixlog.txt to your next reply.

 

[SteveDG]

file attached.

 

[PeterJ]

The log looks good.

Do you still use following programs ?
- Debugging Tools for Windows
- WD Quick View
- WD SmartWare
- Microsoft Windows Performance Toolkit
- Microsoft Windows SDK for Windows 7