Solved Help with upgrade to Windows 11 on Unsupported

Bree said:

When starting an in-place upgrade from a mounted ISO it first copies the files setup will run to the C: drive. You can then replace the copy of appraiserres.dll there.

Disconnect from the internet before starting. Mount the ISO and run the Setup.exe you'll find there. On the first screen click 'Change how Setup downloads updates' and select 'Not right now'. Next replace C:\$WINDOWS.~BT\Sources\appraiserres.dll with an empty dummy file, make one by making a new text document on your desktop and renaming it as appraiserres.dll. You can now continue the install and it will skip the compatibility checks.

Click to expand...

Thanks @Bree , I will try your method before trying @jimbo45 's method. For clarification as outlined in my initial post I mounted ISO and copied contents to a folder on C: Drive, then replaced apparaiseres.dll in extracted Sources folder before running setup. Your method of replacing apparaiseres.dll in C:\$WINDOWS.~BT\Sources I have not tried.
Many thanks

zbook said:

What are your current plans for troubleshooting versus backing up files and a fresh installation?

Had you uninstalled Avast?

Avast Removal Tool | Download Avast Clear | Avast

www.avast.com

Using the Avast Uninstall Tool | Official Avast Support

Step-by-step instructions to use the Avast Uninstall Tool on Windows PC.

support.avast.com

Code:

2024-04-17 12:20:35, Error                 SXS    Mismatched public key token found between manifest and catalog for Policy.14.0.Avast.VC140.MFC, version 14.0.27821.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:12]'win32-policy'

Code:

2024-04-17 12:20:35, Error                 SXS    Finalize failed with 0x8007370f

Click to expand...

I do not have Avast installed. I had Sophos Home which I removed and then ran CCleaner to remove remnants. I have moved all my files onto an external hard drive for safekeeping and have an image of the hard drive as a last resort although it is an old copy and I need to update it as suggested by @jimbo45
Many thanks

wabbit said:

Hello @Fozzie Bear: By chance did you disconnect from the internet before and during your attempts to upgrade? Ever since 22H2 came out, I've always disconnected from the internet when doing in-place upgrades on unsupported devices. There is a chance that if you are connected to the internet during the upgrade, the altered apparaiseres.dll could be overwritten.

Click to expand...

Thanks @wabbit, No on the initial few tries upgrading, I did not connect from the internet but had a lightbulb moment yesterday that the updates could be overwriting the apparaiseres.dll even though I had unchecked download updates. I therefore disconnected from the internet however the result this morning was the same. the only difference is it proceeded to 91% instead of the previous barrier of 89% so not sure what happened.
Is anyone on this forum able to read a decipher the setup error log to pinpoint where the installation actually fails?

Please run the V2 log collector and post a share link into this thread using drop box or google drive.



The setuperr reported:
2024-04-17 12:20:35, Error SXS Mismatched public key token found between manifest and catalog for Policy.14.0.Avast.VC140.MFC, version 14.0.27821.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:12]'win32-policy'

Avast was at one time used?

Run the Avast uninstall tool.

zbook said:

Please run the V2 log collector and post a share link into this thread using drop box or google drive.

BSOD - Posting Instructions

BSOD - Posting Instructions This will show you how to help provide needed information about your system and dump files. It will not contain any personal or sensitive information about you or your data. To get better help with your Windows BSOD issue, please read these instructions and follow...

www.elevenforum.com

The setuperr reported:
2024-04-17 12:20:35, Error SXS Mismatched public key token found between manifest and catalog for Policy.14.0.Avast.VC140.MFC, version 14.0.27821.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:12]'win32-policy'

Avast was at one time used?

Run the Avast uninstall tool.

Click to expand...

Many thanks @zbook . Yes Avast was installed but from memory back when the machine had Windows 7 installed. Since then it has only had Windows Defender or laterly Sophos. I appreciate you highlighting this as I had assumed all traces of Avast would have gone with the upgrade to Windows 10. I learn something new every day. I will run the V2 collector log before and after running the Avast uninstaller

zbook said:

Please run the V2 log collector and post a share link into this thread using drop box or google drive.

BSOD - Posting Instructions

BSOD - Posting Instructions This will show you how to help provide needed information about your system and dump files. It will not contain any personal or sensitive information about you or your data. To get better help with your Windows BSOD issue, please read these instructions and follow...

www.elevenforum.com

The setuperr reported:
2024-04-17 12:20:35, Error SXS Mismatched public key token found between manifest and catalog for Policy.14.0.Avast.VC140.MFC, version 14.0.27821.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:12]'win32-policy'

Avast was at one time used?

Run the Avast uninstall tool.

Click to expand...

Hi @zbook
OK so ran V2 log before doing anything else and uploaded here
I then ran the Avast removal tool and re-ran V2 Log uploaded again here
Finally I tried an upgrade again using the method suggested by @Bree which again failed at 91% with same error message as before. I re-ran V2Log after failed install and uploaded again here
If there is any further information you need please ask.

I am sure there is something other than the hardware non compatibility that is causing this to fail.
I have just thought of this but if it is relevant I have still got a windows.old directory on my C: drive which I cannot remove. Its been there since one of the earlier updates from 1809 and renamed itself to windows.old(1).
I have tried disk clean up, I've tried removing from storage setting and even tried elevated command prompt to take ownership. All the first commands are successful but the final command to delete the folder fails with an error "directory not empty". I wonder if the system is trying to backup the old OS to this folder?

Fozzie Bear said:

I am sure there is something other than the hardware non compatibility that is causing this to fail.

Click to expand...

One of the computer setup.err findings had indicated problems with Avast.





The V2 collected log findings were:

a) Multiple BSOD (first 04/16/2024 and last 04/22/2024)

b) Out of date BIOS

c) Failed Windows fast startup

d) Possible Secure Boot problems




1) Run Tuneup plus > post a share link







2) Turn off Windows fast startup





3) The BIOS Version/Date American Megatrends Inc. F3, 02/05/2013

Upgrade the BIOS to the most up to date non-beta BIOS




4) Run: https://aka.ms/GetPCHealthCheckApp > post a share link




5) Create a new restore point:




6) Read this link on Windows Driver Verifier (WDV):

Could you please provide a copy of your COMPONENTS hive? It should be available in the following file path: %systemroot%\System32\config\COMPONENTS

zbook said:

One of the computer setup.err findings had indicated problems with Avast.





The V2 collected log findings were:

a) Multiple BSOD (first 04/16/2024 and last 04/22/2024)

b) Out of date BIOS

c) Failed Windows fast startup

d) Possible Secure Boot problems




1) Run Tuneup plus > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

2) Turn off Windows fast startup

Turn On or Off Fast Startup in Windows 10

How to Turn On or Off Fast Startup in Windows 10

www.tenforums.com

3) The BIOS Version/Date American Megatrends Inc. F3, 02/05/2013

Upgrade the BIOS to the most up to date non-beta BIOS




4) Run: https://aka.ms/GetPCHealthCheckApp > post a share link

How to check if your device meets Windows 11 system requirements after changing device hardware - Microsoft Support

If you changed your hardware in order to upgrade to Windows 11 and the system is not recognizing the change in a timely manner, this article explains how to initiate the assessment manually.

support.microsoft.com

5) Create a new restore point:

Create System Restore Point in Windows 10

How to Create a System Restore Point in Windows 10

www.tenforums.com

6) Read this link on Windows Driver Verifier (WDV):

Enable and Disable Driver Verifier in Windows 10

How to Enable and Disable Driver Verifier in Windows 10

www.tenforums.com

Click to expand...

Hi @zbook Firstly can I thank you for helping me out.
This is a self built machine and was originally configured as a Hackingtosh running OSX Yosemite. When I got a proper Mac I did a clean install of Windows 7 Ultimate and then upgraded to Windows 10 when it was offered free. Initially I had lots of Blue Screens but they seemed to stop when I updated to 21H2 and then 22H2. Its interesting that the Vlog 2 has picked this up.

I am working my way through your recommendations and have disabled fast boot and checked the Gigabyte website and I am several versions behind so will update the bios. I'll then run Tune Up and report back.
I have scanned the latest setuperr.log and there is nothing related to Avast so I assume that the Avast removal tool has cleaned any remnants.

Fozzie Bear said:

I have scanned the latest setuperr.log and there is nothing related to Avast so I assume that the Avast removal tool has cleaned any remnants.

Click to expand...

I assume that you've attempted another upgrade to Windows 11 then and it failed? Could you please provide the latest copy of your setuperr.log along with a copy of your COMPONENTS hive?

OK so Bios updated and QuickStart disabled, Have run TuneUp Log after and posted here
PC Health Check snip here
Also re-run of V2 log after updating bios and turning off Quick Boot here
I'm currently running Driver Verifier and will post back if I get any blue screens. If I don't what to expect, does Driver Verifier create a log I can upload?

For @x BlueRobot the Component hive is here

Also I don't know if its relevant but here is a screenshot of my drive partitions. I expected a EFI partition and Data Partition (C:) but not two Recovery Partitions and a 16mb Reserved Partition. Is that normal?

Fozzie Bear said:

I'm currently running Driver Verifier and will post back if I get any blue screens. If I don't what to expect, does Driver Verifier create a log I can upload?

Click to expand...

It'll crash your machine with a BSOD and then should hopefully write to the %systemroot%\Minidump directory with a .dmp file. However, depending on your dump file settings, it may also write a larger (and generally more useful) .dmp file called MEMORY.DMP to %systemroot% i.e. %systemroot%\MEMORY.DMP.

Fozzie Bear said:

two Recovery Partitions and a 16mb Reserved Partition. Is that normal?

Click to expand...

The 16MB will be your MSR (Microsoft System Reserved) partition and one of those recovery partitions should be your standard Windows RE partitions. Have you checked the GPT Id of each of those RE partitions? The Windows RE partition should have an Id of: DE94BBA4-06D1-4D40-A16A-BFD50179D6AC

Those avast! keys are still present in your COMPONENTS hive too, I'll prepare a script which will delete them for you.

FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. 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.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

Many thanks @x BlueRobot Below is content of Log
Fix result of Farbar Recovery Scan Tool (x64) Version: 19.04.2024 01
Ran by John (25-04-2024 18:29:43) Run:1
Running from C:\Users\johnf\Desktop
Loaded Profiles: John
Boot Mode: Normal
==============================================

fixlist content:
*****************
cmd: reg load HKEY_LOCAL_MACHINE\COMPONENTS %systemroot%\System32\config\COMPONENTS
DeleteKey: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.27821.0_none_5b87bb4915fad71f
DeleteKey: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc140.mfc_fcc99ee6193ebbca_14.0.27821.0_none_6067bd3b12cf0652
*****************


========= reg load HKEY_LOCAL_MACHINE\COMPONENTS %systemroot%\System32\config\COMPONENTS =========

The operation completed successfully.



========= End of CMD: =========

HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.27821.0_none_5b87bb4915fad71f => removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc140.mfc_fcc99ee6193ebbca_14.0.27821.0_none_6067bd3b12cf0652 => removed successfully

==== End of Fixlog 18:29:44 ====


Ive had no BSOD so assume I can re-try another upgrade after disabling Driver Veryfier?
Thank again for all your help

Fozzie Bear said:

Ive had no BSOD so assume I can re-try another upgrade after disabling Driver Veryfier?

Click to expand...

I would, I personally think this isn't a driver issue. If the upgrade fails again then please provide the setuperr.log like you did before.

I went through your Components subkey again and there's a few other avast subkeys which might end up causing the same issue again, the attached fixlist.txt file will delete those as well.

Sorry for delay in replying but had other work priorities. The latest attempt at an upgrade also failed here is the v2 log file
Her is the result from Fixlog
Fix result of Farbar Recovery Scan Tool (x64) Version: 19.04.2024 01
Ran by John (29-04-2024 13:05:58) Run:2
Running from C:\Users\johnf\Desktop
Loaded Profiles: John
Boot Mode: Normal
==============================================

fixlist content:
*****************
cmd: reg load HKEY_LOCAL_MACHINE\COMPONENTS %systemroot%\System32\config\COMPONENTS
DeleteKey: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.27821.0_none_4e76363ccee8be59
DeleteKey: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.27821.0_none_5356382ecbbced8c
DeleteKey: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.27821.0_none_a334f2202a770025
DeleteKey: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.27821.0_none_a814f412274b2f58
DeleteKey: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.27821.0_none_96236d13e364e75f
DeleteKey: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.27821.0_none_9b036f05e0391692

*****************


========= reg load HKEY_LOCAL_MACHINE\COMPONENTS %systemroot%\System32\config\COMPONENTS =========

The operation completed successfully.



========= End of CMD: =========

HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.27821.0_none_4e76363ccee8be59 => removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.27821.0_none_5356382ecbbced8c => removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.27821.0_none_a334f2202a770025 => removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.27821.0_none_a814f412274b2f58 => removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.27821.0_none_96236d13e364e75f => removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.27821.0_none_9b036f05e0391692 => removed successfully

==== End of Fixlog 13:05:59 ====


I think I need to bit the bullet and do a clean install of Windows 11 on another SSD and see if that is successful but will try one further upgrade after removing the other Avast Reg entries above. Thank again @x BlueRobot

There is no need to do a clean install at all, if it fails after removing those other avast registry keys then we can examine the latest setuperr.log. It isn't unusual for there to be multiple things blocking an in-place upgrade from completing successfully.

Many thanks @x BlueRobot I really appreciate all your help but unfortunately I no longer have the time to keep trying upgrades so have installed another SSD and successfully done a clean install of Windows 11. As as you suspected it was not a hardware but a software/OS issue.

However I now have another issue. I have windows 10 on the old SSD at disk 0 and Windows 11 on a second SSD at disk 1. I could boot between the two using the F12 bios boot option. However I thought I would install EasyBCD to be able to easily dual boot.
For some reason in Windows 11 I could not see the windows 10 SSD in windows explorer or even in Disk Manager so could not install Easy BCD in Win 11. I rebooted to Windows 10 and could see the two Windows 11 partitions in Windows 10 so decided to install EasyBCD.
Unfortunately I duplicated windows 10 boot entries and as a result the BCD Boot screen was a mess. I managed to get back into windows 10 and edited the boot menu in EasyBCD but can therefore no longer boot into Windows 10 so have screwed up the boot loader.
I've now got to repair the boot section of Windows 10. That's the problem with not taking my time Grrrrrr!!!!