Solved In-place Upgrade test Failure

Bastet · Apr 2, 2022

@Ghot I used the registry fix when I first upgraded from Win 10 to 11 & now I used USB installation media & I'd removed the recommended file (appraisererr?) from the sources folder, I did also try removing it from the sources folder on the PC after running the setup, but problem remained.
Is there a more recommended way of doing this?

x BlueRobot · Apr 2, 2022

Bastet said:
No BSOD so far.

Did you check the directory paths I mentioned in my post?

Bastet · Apr 2, 2022

x BlueRobot said:
Did you check the directory paths I mentioned in my post?

As I rolled back to before I tried the upgrade I wondered if there’s anything there.
I checked & neither are shown. I receive an error saying that Windows cannot find the files.

x BlueRobot · Apr 2, 2022

Don't worry, just noticed that you've provided the setupmem.dmp along with your other files in an earlier post. I'll have a look at them now. It's very likely going to be compatibility issue, especially since you bypassed the compatibility checks to begin with.

zbook · Apr 2, 2022

If there are no performance problems or very slow boot please add these customized tests:

Code:

    [ ] 0x00000001 Special pool.
    [ ] 0x00000002 Force IRQL checking.
    [ ] 0x00000008 Pool tracking.
    [ ] 0x00000020 Deadlock detection.
    [ ] 0x00000080 DMA checking.
    [ ] 0x00000100 Security checks.

If there is no immediate BSOD then post a new verifier / querysettings

Then continue to add 4 - 6 customized tests (to match the customized tests in this link) every 3 to four hours if there are no significant performance problems or very slow boot.

Redirecting

x BlueRobot · Apr 2, 2022

This is the first time I've seen a Stop 0x4 and there is no information whatsoever from Microsoft regarding what causes it. However, it appears to be due to WinSetupMon.sys which is part of the setup process and a few people seem to have experienced the same issue when upgrading to Windows 11.

Rich (BB code):

2: kd> knL
 # Child-SP          RetAddr               Call Site
00 ffff9c08`20a2f328 fffff802`3dfde954     nt!KeBugCheck
01 ffff9c08`20a2f330 fffff802`3dfdef99     WinSetupMon!HandleOperation+0x540 << Crash here!
02 ffff9c08`20a2f500 fffff802`21246d34     WinSetupMon!WinSetupMonPreSetInformation+0x59
03 ffff9c08`20a2f560 fffff802`212467e6     FLTMGR!FltpPerformPreCallbacksWorker+0x374
04 ffff9c08`20a2f670 fffff802`21245872     FLTMGR!FltpPassThroughInternal+0xc6
05 ffff9c08`20a2f6c0 fffff802`212455fb     FLTMGR!FltpPassThrough+0x1c2
06 ffff9c08`20a2f730 fffff802`25d02f65     FLTMGR!FltpDispatch+0x8b << Handler routine for the FLT IRP
07 ffff9c08`20a2f790 fffff802`25c97f19     nt!IofCallDriver+0x55 << Calls into Filter Manager engine, all "modern" filter drivers register with this
08 ffff9c08`20a2f7d0 fffff802`25c9871a     nt!IopCallDriverReference+0xf9
09 ffff9c08`20a2f840 fffff802`25e27b75     nt!NtSetInformationFile+0x52a
0a ffff9c08`20a2f970 00007ffa`e0d23844     nt!KiSystemServiceCopyEnd+0x25
0b 00000000`0799e008 00000000`00000000     0x00007ffa`e0d23844

Interestingly, the setup driver was potentially referencing one of your Intel drivers.

Rich (BB code):

               rsp : 0xffff9c0820a2f328 : 0xfffff8023dfde954 : WinSetupMon!HandleOperation+0x540
0xffff9c0820a2f328 : 0xfffff8023dfde954 : WinSetupMon!HandleOperation+0x540
0xffff9c0820a2f348 : 0xfffff8023dfd8430 :  dt WinSetupMon!CWsmTrackingConfig::CTrackingPathInfo
0xffff9c0820a2f3d0 : 0xffff8b8c6639ea10 :  !du ""\Device\HarddiskVolume4\Users\Tau_D\Downloads\Intel Drivers\DSA\Logs\Service\Dev...""
0xffff9c0820a2f400 : 0xfffff8023dfda037 : WinSetupMon!TraceLoggingMetadata+0x6f
0xffff9c0820a2f410 : 0xfffff8023dfd9fe4 : WinSetupMon!TraceLoggingMetadata+0x1c
0xffff9c0820a2f440 : 0xffff8b8c6639ea10 :  !du ""\Device\HarddiskVolume4\Users\Tau_D\Downloads\Intel Drivers\DSA\Logs\Service\Dev...""
0xffff9c0820a2f480 : 0xffff8b8c5f31b5b0 :  !du ""\Device\HarddiskVolume4\Program Files (x86)\Intel\Driver and Support Assistant\D...""
0xffff9c0820a2f4f8 : 0xfffff8023dfdef99 : WinSetupMon!WinSetupMonPreSetInformation+0x59
0xffff9c0820a2f518 : 0xfffff80225c90d6d : nt!ExReleaseCacheAwarePushLockSharedEx+0x7d
0xffff9c0820a2f558 : 0xfffff80221246d34 : FLTMGR!FltpPerformPreCallbacksWorker+0x374
0xffff9c0820a2f668 : 0xfffff802212467e6 : FLTMGR!FltpPassThroughInternal+0xc6
0xffff9c0820a2f6b8 : 0xfffff80221245872 : FLTMGR!FltpPassThrough+0x1c2
0xffff9c0820a2f728 : 0xfffff802212455fb : FLTMGR!FltpDispatch+0x8b
0xffff9c0820a2f788 : 0xfffff80225d02f65 : nt!IofCallDriver+0x55
0xffff9c0820a2f7c8 : 0xfffff80225c97f19 : nt!IopCallDriverReference+0xf9
0xffff9c0820a2f838 : 0xfffff80225c9871a : nt!NtSetInformationFile+0x52a
0xffff9c0820a2f8d8 : 0xfffff80226105638 : nt!NtOpenFile+0x58
0xffff9c0820a2f968 : 0xfffff80225e27b75 : nt!KiSystemServiceCopyEnd+0x25
0xffff9c0820a2f9d8 : 0xfffff80225e27b75 : nt!KiSystemServiceCopyEnd+0x25
0xffff9c0820a2f9e0 : 0xffffe48623f7b080 :  Trap @ ffff9c0820a2f9e0

The string is:

Rich (BB code):

2: kd> !PDE.du ffff8b8c6639ea10
\Device\HarddiskVolume4\Users\Tau_D\Downloads\Intel Drivers\DSA\Logs\Service\Devices.xml.bak

Looks like the Intel Driver Support Assistant logs? There's a log file for the driver under $WINDOWS.~BT\Sources\Rollback\WinSetupMon.log which appears to initiate some form of file tracking? Presumably so it can rollback if needed?

From your setuperr.log:

Rich (BB code):

2022-04-01 13:28:19, Error                 SP     Cannot map user hive C:\Users\Default\NTUSER.DAT in HKEY_USERS\S-1-0-0. Error: 0x00000020
2022-04-01 13:28:19, Error                 CSI    00000006@2022/4/1:13:28:19.538 (F) onecore\base\wcp\sil\ntsystem.cpp(5047): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
[gle=0x80004005]
2022-04-01 13:28:19, Error                 CONX   aepic: ERROR,AeWERQueryFileInfo,171,RegLoadAppKey failed [2]

Could you please enter the following command from a command prompt:

Rich (BB code):

reg query HKEY_USERS\S-1-0-0

Followed by:

Rich (BB code):

reg query HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-0-0

The key seems to be missing. That particular SSID corresponds to the null user; a generic default user SID.

From setup.api.upgrade:

Rich (BB code):

>>>  [Device Install (Hardware initiated) - SWD\PRINTENUM\WSD-6f7c7306-564f-4e7e-8668-08b894cc8229]
>>>  Section start 2022/04/01 12:20:20.823
     ump: Install needed due to device needing additional installation
     utl: {Select Drivers - SWD\PRINTENUM\WSD-6f7c7306-564f-4e7e-8668-08b894cc8229} 12:20:20.938
     utl:      Driver Node:
     utl:           Status         - Selected
     utl:           Driver INF     - oem8.inf (C:\WINDOWS\System32\DriverStore\FileRepository\ip72006xps.inf_amd64_bfc2437030874200\ip72006xps.inf)
     utl:           Class GUID     - {4d36e979-e325-11ce-bfc1-08002be10318}
     utl:           Driver Version - 05/23/2012,5.60.2.40
     utl:           Configuration  - WSDPRINT\CanoniP7200_seriesEDEA
     utl:           Driver Rank    - 00FF1200
     utl:           Signer Score   - WHQL (0D000005)
     utl:      Driver Node:
     utl:           Status         - Outranked
     utl:           Driver INF     - prnms013.inf (C:\WINDOWS\System32\DriverStore\FileRepository\prnms013.inf_amd64_ae94ada6e6def772\prnms013.inf)
     utl:           Class GUID     - {62f9c741-b25a-46ce-b54c-9bccce08b6f2}
     utl:           Driver Version - 06/21/2006,10.0.22000.1
     utl:           Configuration  - CID_MS_GENERICPRINT [MS_GENERICPRINT]
     utl:           Driver Rank    - 00FF3002
     utl:           Signer Score   - Inbox (0D000003)
     utl:      Driver Node:
     utl:           Status         - Outranked
     utl:           Driver INF     - c_swdevice.inf (C:\WINDOWS\System32\DriverStore\FileRepository\c_swdevice.inf_amd64_655de2ccc6addd01\c_swdevice.inf)
     utl:           Class GUID     - {62f9c741-b25a-46ce-b54c-9bccce08b6f2}
     utl:           Driver Version - 06/21/2006,10.0.22000.1
     utl:           Configuration  - SWD\GenericRaw [SoftwareDevice]
     utl:           Driver Rank    - 00FF3003
     utl:           Signer Score   - Inbox (0D000003)
     utl: {Select Drivers - exit(0x00000000} 12:20:21.010
!    dvi: Device class {4d36e979-e325-11ce-bfc1-08002be10318} is not configurable.
     dvi: Searching for hardware ID(s):
     dvi:      wsdprint\canonip7200_seriesedea
     dvi:      canonip7200_seriesedea
     dvi: Searching for compatible ID(s):
     dvi:      wsdprint\1284_cid_ca_ivec1type1_ijp
     dvi:      1284_cid_ca_ivec1type1_ijp
     dvi:      cid_ms_genericprint
     dvi:      swd\genericraw
     dvi:      swd\generic
     dvi: Class GUID of device changed to: {4d36e979-e325-11ce-bfc1-08002be10318}.
     dvi: Waiting for previous device install to complete. 12:20:21.073
     ndv: {Core Device Install} 12:20:43.091
     dvi:      {Install Device - SWD\PRINTENUM\WSD-6F7C7306-564F-4E7E-8668-08B894CC8229} 12:20:43.100
     dvi:           Device Status: 0x0180200a
     dvi:           Config Flags: 0x00000000
     dvi:           Parent Device: SWD\DAFWSDProvider\urn:uuid:00000000-0000-1000-8000-180caccc590e/http://schemas.canon.com/Printer
     dvi:           {DIF_ALLOW_INSTALL} 12:20:43.136
     dvi:                Using exported function 'ClassInstall32' in module 'C:\WINDOWS\system32\ntprint.dll'.
     dvi:                Class installer == ntprint.dll,ClassInstall32
     dvi:                Class installer: Enter 12:20:43.168
     dvi:                Class installer: Exit
     dvi:                Default installer: Enter 12:20:43.184
     dvi:                Default installer: Exit
     dvi:           {DIF_ALLOW_INSTALL - exit(0xe000020e)} 12:20:43.198
     dvi:           {DIF_INSTALLDEVICEFILES} 12:20:43.203
     dvi:                Class installer: Enter 12:20:43.209
     inf:                     {Install from INF Section - CNM_0406XPS_VISTA} 12:20:43.232
     inf:                          Flags         - 0x000007ef
     inf:                     {Install from INF Section - exit(0x00000000)} 12:20:43.249
     dvi:                Class installer: Exit
     dvi:           {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 12:20:49.324
     dvi:           {DIF_REGISTER_COINSTALLERS} 12:20:49.336
     dvi:                Reset Device: Resetting device configuration. 12:20:49.344
     dvi:                Reset Device: Resetting device configuration completed. 12:20:49.352
     dvi:                Class installer: Enter 12:20:49.359
     dvi:                Class installer: Exit
     dvi:                Default installer: Enter 12:20:49.373
     inf:                     {Install from INF Section - CNM_0406XPS_VISTA.CoInstallers} 12:20:49.381
     inf:                          Flags         - 0x001001ee
     inf:                     {Install from INF Section - exit(0x00000000)} 12:20:49.395
     dvi:                Default installer: Exit
     dvi:           {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 12:20:49.410
     dvi:           {DIF_INSTALLINTERFACES} 12:20:49.416
     dvi:                Class installer: Enter 12:20:49.424
     dvi:                Class installer: Exit
     dvi:                Default installer: Enter 12:20:49.434
     dvi:                Default installer: Exit
     dvi:           {DIF_INSTALLINTERFACES - exit(0x00000000)} 12:20:49.447
     dvi:           {DIF_INSTALLDEVICE} 12:20:49.455
     dvi:                Class installer: Enter 12:20:49.460
!!!  dvi:                Class installer: failed(0x00000490)!
!!!  dvi:                Error 1168: Element not found.
     dvi:           {DIF_INSTALLDEVICE - exit(0x00000490)} 12:20:49.497
!!!  dvi:           Error(00000490) installing device!
     dvi:      {Install Device - exit(0x00000490)} 12:20:49.511
     dvi: {Core Device Install - exit(0x00000490)} 12:20:49.517
     dvi: {DIF_DESTROYPRIVATEDATA} 12:20:49.524
     dvi:      Class installer: Enter 12:20:49.531
     dvi:      Class installer: Exit
     dvi:      Default installer: Enter 12:20:49.548
     dvi:      Default installer: Exit
     dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 12:20:49.563
<<<  Section end 2022/04/01 12:20:49.578
<<<  [Exit status: FAILURE(0x00000490)]

It does appear there was some form of compatibility issue with your printer driver as well.

There appears to be multiple possible problems here. I would strongly recommend that you clean install Windows 10 again since that is known to be compatible with your machine. These issues are why I've very concerned with users posting tips on how to bypass compatibility checks, they exist for a reason and the build will break eventually as shown here.

Bastet · Apr 2, 2022

@x BlueRobot
Cmd output attached.
I uninstalled all Printer drivers in a previous test & problem remained.
The irony is I upgraded to Win 11 smoothly from windows 10 it is only the in-place repair which is failing. I would've expected that to fail as well if components weren't compatible.
If I uninstalled Driver support assistant would the problem remain?
It is looking more & more like I need to restore my Win 10 image.

zbook · Apr 2, 2022

Consider deleting appraisers if WDV finds no misbehaving drivers.

If the in place upgrade fails then submit new log files.

Bastet · Apr 2, 2022

zbook said:
Consider deleting appraisers if WDV finds no misbehaving drivers.

If the in place upgrade fails then submit new log files.

Did that first time. during the install I removed the file from the PC which didn't work, then I tried again & removed the file from the USB installation media. I also used the registry fix before upgrading from Win 10.

zbook · Apr 2, 2022

When it failed was there an error message or code?

If there are no performance problems you can race through the WDV testing using more customized tests.

What are the status of the computer files?
Are there important files that need to be saved?
Are there important applications that cannot be reinstalled?

In case the above method fails then you may be able to perform a custom install:
(saves files into windows.old, install new operating system) (drivers and applications need to be reinstalled)

Bastet · Apr 2, 2022

Same one as I originally posted.

zbook · Apr 2, 2022

The prior post was edited before seeing the latest post.

Bastet · Apr 2, 2022

The bluescreen error was invalid data access trap & second boot phase with sysprep_respecialize.

zbook · Apr 2, 2022

Were there any performance problems so far using WDV?

Are you up to 9 customized tests?

Can you uninstall all printers?

Bastet · Apr 2, 2022

No problems so far.
Yes.
Printer was uninstalled previously (but were reinstalled when I restored an image) so I suspect it wouldn’t be any different if I did so again.

zbook · Apr 2, 2022

Please post a new verifier /querysettings

Ghot · Apr 2, 2022

@Bastet
I'm just guessing here... we're kind of in unknown waters.

I would try the following...

0. If you have room, make a backup of your Windows 11 install.
1. Then, restore the Windows 10 image (since we know you can upgrade to Win 11 already).
2. Then, try an In-Place upgrade from Windows 10 to Windows 10, and see if THAT works.
2a. Cause if THAT doesn't work... I doubt it will work on Windows 11 with work arounds.

In other words... make sure the In-Place upgrade works on Windows 10. If it does, then do the "upgrade" to Windows 11, again, and use the "appraiser" method, this time.
Then, when you again try the In-Place upgrade on Windows 11, do the appraiser method also.

Or to put it another way... make sure that the Win 11 upgrade, and the Win 11 to Win 11 In-Place upgrade are using the "same" compatibility work around method.

Note: This In-Place upgrade problem you're having on Win 11, might also be one of the things Microsoft was hinting at, when they said that Win 11 won't work (completely), on non-compatible devices.

I'm also curious as to whether "anyone" on a Win 11 install on a non-compatible machine, has been able to do a Win11 to Win 11 In-Place upgrade.

Maybe, the In-Place upgrade is "repairing" those registry tweaks that allowed you to install Win 11 in the 1st place, and then that may be why the In-Place upgrade is failing. Because it can now "see" that the machine can't run Win 11?

Bastet · Apr 2, 2022

zbook said:
Please post a new verifier /querysettings

Bastet · Apr 2, 2022

@Ghot Yes, the in-place repair works on Windows 10. I tested that prior to upgrading. The question is do I need to run the registry fix bat again before the in-place repair?
I tried the Appraiser workaround before (by removing it from the installation media) & it didn't work.

zbook · Apr 2, 2022

If there are no significant performance problems or very slow boot then add:

Code:

    [ ] 0x00000800 Miscellaneous checks.
    [ ] 0x00020000 DDI compliance checking.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.
    [ ] 0x00008000 Power framework delay fuzzing.
    [ ] 0x00010000 Port/miniport interface checking.
    [ ] 0x00040000 Systematic low resources simulation.
    [ ] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

If there is no immediate BSOD then post a new verifier /querysettings