Solved Win10 to Win11 fails with 0xC1900101 - 0x40017 on second reboot

Hi zbook, here are the requested file captured before attempting drive verifier - non gui

1) Please post a new V2 share link into the newest post.

2) Run chkdskfromevent.bat > post a share link - attached to thread
chkdskFromEvent.log


3) These are new trial and error PS commands to run WDV:
In case these trial and error commands fail post share links.

Still fails - attached error text files
verifier group a-d ps cmd line.txt
verifier querysettings.txt


Setup group a via giu

Here is group a setup
C:\WINDOWS\system32>verifier /querysettings

Verifier Flags: 0x001a6018

Standard Flags:

[ ] 0x00000001 Special pool.
[ ] 0x00000002 Force IRQL checking.
[X] 0x00000008 Pool tracking.
[X] 0x00000010 I/O verification.
[ ] 0x00000020 Deadlock detection.
[ ] 0x00000080 DMA checking.
[ ] 0x00000100 Security checks.
[ ] 0x00000800 Miscellaneous checks.
[X] 0x00020000 DDI compliance checking.

Additional Flags:

[ ] 0x00000004 Randomized low resources simulation.
[ ] 0x00000200 Force pending I/O requests.
[ ] 0x00000400 IRP logging.
[X] 0x00002000 Invariant MDL checking for stack.
[X] 0x00004000 Invariant MDL checking for driver.
[ ] 0x00008000 Power framework delay fuzzing.
[ ] 0x00010000 Port/miniport interface checking.
[ ] 0x00040000 Systematic low resources simulation.
[X] 0x00080000 DDI compliance checking (additional).
[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.

Internal Flags:

[X] 0x00100000 Extended Verifier flags (internal).

[X] Indicates flag is enabled.

Boot Mode:

Persistent

Rules:

All rules are using default settings

Extensions:

wdm: rules.all

Verified Drivers:

nllelam.sys
iastorac.sys
pxhlpa64.sys
nllvmm.sys
nllrvrt.sys
pwdrvio.sys
nllbuniv.sys
nllbidsh.sys
nllardisk.sys
ambakdrv.sys
vboxnetadp6.sys
dbutildrv2.sys
nvlddmkm.sys
igdkmd64.sys
btfilter.sys
teedriverw8x64.sys
qcamain10x64.sys
e2xw10x64.sys
cthdb.sys
ialpss2_uart2.sys
ialpss2_gpio2.sys
dellinstrumentation.sys
nvhda64v.sys
cthda.sys
rtkvhd64.sys
intcdaud.sys
scrhiddriver3.sys
leqdusb.sys
nllkbd.sys
lhideqd.sys
lhidfilt.sys
lmoufilt.sys
nllsp.sys
nllsnx.sys
nllmonflt.sys
cimfs.sys
nllrdr2.sys
vboxnetlwf.sys
nllnethub.sys
veracrypt.sys
vboxusbmon.sys
vboxsup.sys
nllbidsdriver.sys
nllarpot.sys
hwinfo64a_191.sys
hwinfo64a_190.sys
hwinfo64a_187.sys
hwinfo64a_180.sys
hwinfo64a_178.sys
hwinfo64a_177.sys
hwinfo64a_174.sys
hwinfo64a_172.sys
hwinfo64a_171.sys
hwinfo64a_167.sys
hwinfo64a_165.sys
hwinfo64a_164.sys
hwinfo64a_156.sys
hwinfo64a_153.sys
hwinfo64a_150.sys
dump_diskdump.sys
dump_iastorac.sys
dump_dumpfve.sys
mbamchameleon.sys
ammntdrv.sys
amwrtdrv.sys
000.fcl
googledrivefs31931.sys
kfeco10x64.sys
npf.sys
nllstm.sys
ahflt.sys
mbamswissarmy.sys
mwac.sys
farflt.sys
mbae.sys
mbam.sys
semav6msr64.sys

C:\WINDOWS\system32>will now reboot and will update

PC restarted PC with Group a enabled with no apparent issues/BSOD - let PC run approx 45 minutes. Attached Group a completed - no bsod.txt

Will run verify / reset, reboot and setup Group b and repeat this process

Setup group b via giu

Here is group b setup

C:\WINDOWS\system32>verifier /querysettings

Verifier Flags: 0x01918801

Standard Flags:

[X] 0x00000001 Special pool.
[ ] 0x00000002 Force IRQL checking.
[ ] 0x00000008 Pool tracking.
[ ] 0x00000010 I/O verification.
[ ] 0x00000020 Deadlock detection.
[ ] 0x00000080 DMA checking.
[ ] 0x00000100 Security checks.
[X] 0x00000800 Miscellaneous checks.
[ ] 0x00020000 DDI compliance checking.

Additional Flags:

[ ] 0x00000004 Randomized low resources simulation.
[ ] 0x00000200 Force pending I/O requests.
[ ] 0x00000400 IRP logging.
[ ] 0x00002000 Invariant MDL checking for stack.
[ ] 0x00004000 Invariant MDL checking for driver.
[X] 0x00008000 Power framework delay fuzzing.
[X] 0x00010000 Port/miniport interface checking.
[ ] 0x00040000 Systematic low resources simulation.
[ ] 0x00080000 DDI compliance checking (additional).
[ ] 0x00200000 NDIS/WIFI verification.
[X] 0x00800000 Kernel synchronization delay fuzzing.
[X] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.

Internal Flags:

[X] 0x00100000 Extended Verifier flags (internal).

[X] Indicates flag is enabled.

Boot Mode:

Persistent

Rules:

All rules are using default settings

Verified Drivers:

nllelam.sys
iastorac.sys
pxhlpa64.sys
nllvmm.sys
nllrvrt.sys
pwdrvio.sys
nllbuniv.sys
nllbidsh.sys
nllardisk.sys
ambakdrv.sys
vboxnetadp6.sys
dbutildrv2.sys
nvlddmkm.sys
igdkmd64.sys
btfilter.sys
teedriverw8x64.sys
qcamain10x64.sys
e2xw10x64.sys
cthdb.sys
ialpss2_uart2.sys
ialpss2_gpio2.sys
dellinstrumentation.sys
nvhda64v.sys
cthda.sys
rtkvhd64.sys
intcdaud.sys
scrhiddriver3.sys
leqdusb.sys
nllkbd.sys
lhideqd.sys
lhidfilt.sys
lmoufilt.sys
nllsp.sys
nllsnx.sys
nllmonflt.sys
cimfs.sys
nllrdr2.sys
vboxnetlwf.sys
nllnethub.sys
veracrypt.sys
vboxusbmon.sys
vboxsup.sys
nllbidsdriver.sys
nllarpot.sys
hwinfo64a_191.sys
hwinfo64a_190.sys
hwinfo64a_187.sys
hwinfo64a_180.sys
hwinfo64a_178.sys
hwinfo64a_177.sys
hwinfo64a_174.sys
hwinfo64a_172.sys
hwinfo64a_171.sys
hwinfo64a_167.sys
hwinfo64a_165.sys
hwinfo64a_164.sys
hwinfo64a_156.sys
hwinfo64a_153.sys
hwinfo64a_150.sys
dump_diskdump.sys
dump_iastorac.sys
dump_dumpfve.sys
mbamchameleon.sys
ammntdrv.sys
amwrtdrv.sys
000.fcl
googledrivefs31931.sys
kfeco10x64.sys
npf.sys
nllstm.sys
ahflt.sys
mbamswissarmy.sys
mwac.sys
farflt.sys
mbae.sys
mbam.sys
semav6msr64.sys

C:\WINDOWS\system32>

will now reboot Group b and will update

PC restarted PC with Group b enabled with no apparent issues/BSOD - let PC run approx 1 hr. Attached Group B completed - no bsod.txt

Will run verify / reset, reboot and setup Group c and repeat this process

Setup group c via giu

Here is group c setup

C:\WINDOWS\system32>verifier /querysettings

Verifier Flags: 0x02100000

Standard Flags:

[ ] 0x00000001 Special pool.
[ ] 0x00000002 Force IRQL checking.
[ ] 0x00000008 Pool tracking.
[ ] 0x00000010 I/O verification.
[ ] 0x00000020 Deadlock detection.
[ ] 0x00000080 DMA checking.
[ ] 0x00000100 Security checks.
[ ] 0x00000800 Miscellaneous checks.
[ ] 0x00020000 DDI compliance checking.

Additional Flags:

[ ] 0x00000004 Randomized low resources simulation.
[ ] 0x00000200 Force pending I/O requests.
[ ] 0x00000400 IRP logging.
[ ] 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.
[X] 0x02000000 Code integrity checks.

Internal Flags:

[X] 0x00100000 Extended Verifier flags (internal).

[X] Indicates flag is enabled.

Boot Mode:

Persistent

Rules:

All rules are using default settings

Verified Drivers:

nllelam.sys
iastorac.sys
pxhlpa64.sys
nllvmm.sys
nllrvrt.sys
pwdrvio.sys
nllbuniv.sys
nllbidsh.sys
nllardisk.sys
ambakdrv.sys
vboxnetadp6.sys
dbutildrv2.sys
nvlddmkm.sys
igdkmd64.sys
btfilter.sys
teedriverw8x64.sys
qcamain10x64.sys
e2xw10x64.sys
cthdb.sys
ialpss2_uart2.sys
ialpss2_gpio2.sys
dellinstrumentation.sys
nvhda64v.sys
cthda.sys
rtkvhd64.sys
intcdaud.sys
scrhiddriver3.sys
leqdusb.sys
nllkbd.sys
lhideqd.sys
lhidfilt.sys
lmoufilt.sys
nllsp.sys
nllsnx.sys
nllmonflt.sys
cimfs.sys
nllrdr2.sys
vboxnetlwf.sys
nllnethub.sys
veracrypt.sys
vboxusbmon.sys
vboxsup.sys
nllbidsdriver.sys
nllarpot.sys
hwinfo64a_191.sys
hwinfo64a_190.sys
hwinfo64a_187.sys
hwinfo64a_180.sys
hwinfo64a_178.sys
hwinfo64a_177.sys
hwinfo64a_174.sys
hwinfo64a_172.sys
hwinfo64a_171.sys
hwinfo64a_167.sys
hwinfo64a_165.sys
hwinfo64a_164.sys
hwinfo64a_156.sys
hwinfo64a_153.sys
hwinfo64a_150.sys
dump_diskdump.sys
dump_iastorac.sys
dump_dumpfve.sys
mbamchameleon.sys
ammntdrv.sys
amwrtdrv.sys
000.fcl
googledrivefs31931.sys
kfeco10x64.sys
npf.sys
nllstm.sys
ahflt.sys
mbamswissarmy.sys
mwac.sys
farflt.sys
mbae.sys
mbam.sys
semav6msr64.sys

C:\WINDOWS\system32>

will now reboot Group c and will update

After setting up Group c my pc will not boot. It stuck7on the Dell splash screen. I went to the RE environment and attempted a System Restore. It says there are no Restore files on my pc. Since staring this process I created 3 system restores. The last one I created was just before starting today's verifier process. I then went to cmd prompt and tried verifier /query settings and there are no settings present. I also tried verifier /reset and verifier /bootmode resetonbootfail. I also switched to the system drive and tried both reset commands.
So now I'm stuck.
What do I need to do next?

Please boot to Windows 11 MCT /iso that was used to run chkdsk in Windows RE.


(Option seven)


Open command prompt.

Type:

verifier /reset

or

verifier /bootmode resetonbootfail

Check again for:

CreationTime Description SequenceNumber EventType RestorePointType
------------ ----------- -------------- --------- ----------------
5/8/2026 3:36:10 PM 2nd attempt at verifier 889 BEGIN_SYSTEM_CHANGE 16






In Windows RE:

Type:

Notepad
notepad
bcdedit | find "osdevice"

dism /Image:W:\Mount /Get-Drivers

(change the drive letter W: to the drive letter in the prior command)

(save to notepad then flash drive as needed)

Post an image or share link.

Hi zbook, RE environment still can't find any Restore points.

Something strange is now going on.
1. The bcdedit | find "osdrive" comand doesn't find "osdrive" This worked in the past.
I had to use the bcdedit command with no parms to confirm the "C drive" is the E drive when in the RE environment

2. The dism /Image:E:\Mount /Get-Drivers throws an Error 2
X:\sources>dism /Image:E:\Mount /Get-Drivers

Deployment Image Servicing and Management tool
Version: 10.0.26100.7920

Error: 2

Unable to access the image.
Make sure that the image path and the Windows directory for the image exist and you have Read permissions on the folder.

The DISM log file can be found at X:\windows\Logs\DISM\dism.log

The contents of the dism.log are pasted below

3. The inability to reset the verifier parms

4. Not able to see any restore points

5. and of course the boot hang


Here is the contents of the \windows\Logs\DISM\dism.log file



2026-05-10 13:05:16, Info DISM PID=1868 TID=1864 Scratch directory set to 'X:\windows\SystemTemp\'. - CDISMManager:ut_ScratchDir
2026-05-10 13:05:16, Info DISM PID=1868 TID=1864 DismCore.dll version: 10.0.26100.8246 - CDISMManager::FinalConstruct
2026-05-10 13:05:16, Info DISM Initialized Panther logging at X:\windows\Logs\DISM\dism.log
2026-05-10 13:05:16, Warning DISM PID=1868 TID=1864 Failed to archive the log file. Continuing with existing log file. - CDISMManager::CreateLocalImageSession(hr:0x80070002)
2026-05-10 13:05:16, Info DISM PID=1868 TID=1864 Successfully loaded the ImageSession at "X:\sources" - CDISMManager::LoadLocalImageSession
2026-05-10 13:05:16, Info DISM Initialized Panther logging at X:\windows\Logs\DISM\dism.log
2026-05-10 13:05:16, Info DISM DISM Provider Store: PID=1868 TID=1864 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2026-05-10 13:05:16, Info DISM Initialized Panther logging at X:\windows\Logs\DISM\dism.log
2026-05-10 13:05:16, Info DISM DISM Manager: PID=1868 TID=1864 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2026-05-10 13:05:16, Info DISM DISM.EXE:
2026-05-10 13:05:16, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
2026-05-10 13:05:16, Info DISM DISM.EXE:
2026-05-10 13:05:16, Info DISM DISM.EXE: Host machine information: OS Version=10.0.26100, Running architecture=amd64, Number of processors=8
2026-05-10 13:05:16, Info DISM DISM.EXE: Instance information: Parent process=X:\Windows\System32\cmd.exe, Parent process PID=2924
2026-05-10 13:05:16, Info DISM DISM.EXE: Dism.exe version: 10.0.26100.7920
2026-05-10 13:05:16, Info DISM DISM.EXE: Executing command line: dism /Image:E:\Mount /Get-Drivers
2026-05-10 13:05:16, Warning DISM DISM Provider Store: PID=1868 TID=1864 Failed to retrieve the Provider Instance. - CDISMProviderStore::Internal_GetProvider(hr:0x80004005)
2026-05-10 13:05:16, Info DISM DISM VHD Provider: PID=1868 TID=1864 [E:\Mount] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2026-05-10 13:05:16, Info DISM DISM Imaging Provider: PID=1868 TID=1864 The provider VHDManager does not support CreateDismImage on E:\Mount - CGenericImagingManager::CreateDismImage
2026-05-10 13:05:16, Info DISM DISM WIM Provider: PID=1868 TID=1864 [E:\Mount] does not exist and is not a WIM mount point. - CWimMountedImageInfo::Initialize
2026-05-10 13:05:16, Info DISM DISM Imaging Provider: PID=1868 TID=1864 The provider WimManager does not support CreateDismImage on E:\Mount - CGenericImagingManager::CreateDismImage
2026-05-10 13:05:16, Info DISM DISM Imaging Provider: PID=1868 TID=1864 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage
2026-05-10 13:05:16, Info DISM DISM WIM Provider: PID=1868 TID=1864 [E:\Mount] does not exist and is not a WIM mount point. - CWimMountedImageInfo::Initialize
2026-05-10 13:05:16, Error DISM FolderManager: PID=1868 onecore\base\ntsetup\opktools\dism\providers\folderprovider\dll\FolderImage.h:196 - CFolderImage::CreateFolderImage(hr:0x80070032)
2026-05-10 13:05:16, Info DISM DISM VHD Provider: PID=1868 TID=1864 [E:\Mount] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2026-05-10 13:05:16, Error DISM DISM.EXE: Failed to access the image folder or image's windows folder.
2026-05-10 13:05:16, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2026-05-10 13:05:16, Info DISM DISM.EXE:
2026-05-10 13:05:16, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2026-05-10 13:05:16, Info DISM DISM.EXE:

Did something happen to the windows volume preventing the proper access to execute these commands?
Your thoughts?

Also moving forward, I did make a Macrium Reflect windows image on 5 May plus I have some other smaller backups thru 8 May (all user folders and doc folders) in case I need to restore to a working

My preference is to resolve the win11 update - I really don't want to have to do a clean win11 install unless I have to. I only prepared for the in place upgrade. There is a lot of other preparation I will need to do if forced to do a clean install.

Thanks
Barry

Please perform the following steps:



1) Type > post images or share links

bcdedit
bcdedit | find "osdevice"



2) If bcdedit fails then restore a Macrium backup image



3) After restoring Macrium:



a) Add WMIC:

DISM /Online /Add-Capability /CapabilityName:WMIC~~~~





b) Enable regback:





c) Run Tuneup plus > post a share link







d) Uninstall these software using the applicable uninstall tools:



1) Norton:


Reboot



2) McAfee:


Reboot



3) Malwarebytes:


Reboot



e) Update defender




f) Download Memory integrity system readiness scan tool from Official Microsoft Download Center


AMD

hvciscan_amd64.exe




g) Open administrative command prompt and copy and paste:

cd /users /BarryD /downloads

hvciscan_amd64.exe

Post a share link




h) Place the computer into clean boot:





i) Upgrade Windows performing an in place upgrade repair using the MCT / iso flash drive while in clean boot:





j) For any failure post new:


1) V2:



2) upgrade_failure_info.bat

Hi zbook,

1) Type > post images or share links

bcdedit
bcdedit | find "osdevice"


Here is the output:
Microsoft Windows [Version 10.0.26100.8246]
(c) Microsoft Corporation. All rights reserved.

X:\sources>notepad

X:\sources>bcdedit

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume5
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
resumeobject {582ab720-471c-11f1-b960-b068e6826dca}
displayorder {default}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {default}
device partition=E:
path \WINDOWS\system32\winload.efi
description Windows 10
locale en-US
inherit {bootloadersettings}
recoverysequence {04beb81c-ce18-11ea-b7dd-c18fa662a098}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=E: <-------------------------------------------
systemroot \WINDOWS
resumeobject {ca1c3908-ce17-11ea-b7db-b068e6826dca}
nx OptIn
bootmenupolicy Standard
bootstatuspolicy IgnoreAllFailures
hypervisorlaunchtype Auto

X:\sources>bcdedit | find "osdevice
FIND: Parameter format not correct

X:\sources>bcdedit | find "osdevice"
osdevice partition=E: <------------------------------- command worked this time?????



Not sure why the osdevice flag is now present


=================================================


2) If bcdedit fails then restore a Macrium backup image

Even though bcdedit cmd returned the proper response I wen ahead and restored my Macrium Win10 image successfully and Win10 boots okay


=================================================


3) After restoring Macrium:

a) Add WMIC:

DISM /Online /Add-Capability /CapabilityName:WMIC~~~~


Here's the command output
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell Underwater architecture

PS C:\WINDOWS\system32> DISM /Online /Add-Capability /CapabilityName:WMIC~~~~

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Image Version: 10.0.19045.6466


Error: 87

A Windows capability name was not recognized.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
PS C:\WINDOWS\system32>

Here's the link for dism.log



=================================================


b) Enable regback:
Competed


=================================================


c) Run Tuneup plus > post a share link



=================================================


d) Uninstall these software using the applicable uninstall tools:
1) Norton:
2) McAfee:
3) Malwarebytes:

All 3 completed.


=================================================


e) Update defender - completed


=================================================


f) Download Memory integrity system readiness scan tool from Official Microsoft Download Center

Here's the output:
Microsoft Windows [Version 10.0.19045.6466]
(c) Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>f:

F:\>cd win11 upgrade failure\5-11-26

F:\win11 upgrade failure\5-11-26>hvciscan_amd64.exe
VbsGetIssues: 0x000010C0
UEFI WX Memory Attributes Table required
ACPI WSMT table required
APICV (deprecated)
VbsIsRecommended: 0
HVCI incompatible driver scan start...
HVCI: Error 1168 querying "C:\WINDOWS\System32\DriverStore\FileRepository\dddriver64dcsa.inf_amd64_3bed6326b6d247ae\dddriver64Dcsa.sys" in the SDB
HVCI: "C:\WINDOWS\System32\DriverStore\FileRepository\remoteusblan.inf_amd64_f78905a23bcbcce5\amd64\rcblan.sys" failed with compliance failure mask 00000202
HVCI: "C:\WINDOWS\System32\DriverStore\FileRepository\wdcsam.inf_amd64_7ce69fc8798d6116\wdcsam64_prewin8.sys" failed with compliance failure mask 00000202
HVCI: Error 1168 querying "C:\WINDOWS\System32\drivers\dddriver64Dcsa.sys" in the SDB
HVCI: "C:\WINDOWS\System32\Drivers\PxHlpa64.sys" failed with compliance failure mask 00000202
HVCI: Driver scanning complete
HVCI: scan get result failed.

F:\win11 upgrade failure\5-11-26>


=================================================



I stopped here for today since there were errors in the scripts completed today.
Will await further instructions regarding them

I successfully created a new Macrium Windows backup when finished with the above steps

Thanks
Barry

1) Please post a new V2 share link into the newest post



2) Open administrative command prompt and copy and paste:

fltmc

dism /online /get-drivers /format:table >c:\drivers.txt

Post share links. (the second command creates a desktop file)



3) Open administrative command prompt and copy and paste:

md C:\Drivers
PnpUtil /export-driver * C:\Drivers
pnputil /delete-driver oem6.inf /uninstall /force
ren c:\windows\system32\drivers\wdcsam64_prewin8.sys wdcsam64_prewin8.sys.old
ren c:\windows\system32\drivers\pxhlpa64.sys pxhlpa64.sys.old
ren c:\windows\system32\drivers\rcblan.sys rcblan.sys.old

Post a share link
(right click on the top bar of the administrative command prompt > hover over edit > click select all > right click on the top bar of the administrative command prompt > hover over edit > click copy > paste into the thread)


4) Rerun memory integrity > post a share link


5) Open administrative command prompt and copy and paste:

rundll32.exe c:\windows\system32\pnpclean.dll,RunDLL_PnpClean /drivers /maxclean


6) Reboot


7) Perform an in place upgrade repair while in clean boot

Hi zbook


1) Please post a new V2 share link into the newest post

2) Open administrative command prompt and copy and paste:

fltmc

Microsoft Windows [Version 10.0.19045.6466]
(c) Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>fltmc

Filter Name Num Instances Altitude Frame
------------------------------ ------------- ------------ -----
bindflt 2 409800 0
FsDepends 13 407000 0
UCPD 13 385250.5 0
ahflt 10 385250.1 0
WdFilter 13 328010 0
storqosflt 0 244000 0
wcifs 3 189900 0
dbx 8 186500 0
CldFlt 1 180451 0
FileCrypt 2 141100 0
luafv 1 135000 0
npsvctrig 1 46000 0
Wof 10 40700 0
FileInfo 13 40500 0

C:\WINDOWS\system32>


dism /online /get-drivers /format:table >c:\drivers.txt


3) Open administrative command prompt and copy and paste:

md C:\Drivers
PnpUtil /export-driver * C:\Drivers
pnputil /delete-driver oem6.inf /uninstall /force
ren c:\windows\system32\drivers\wdcsam64_prewin8.sys wdcsam64_prewin8.sys.old
ren c:\windows\system32\drivers\pxhlpa64.sys pxhlpa64.sys.old
ren c:\windows\system32\drivers\rcblan.sys rcblan.sys.old


C:\>ren c:\windows\system32\drivers\wdcsam64_prewin8.sys wdcsam64_prewin8.sys.old
The system cannot find the file specified.

C:\>ren c:\windows\system32\drivers\pxhlpa64.sys pxhlpa64.sys.old

C:\>ren c:\windows\system32\drivers\rcblan.sys rcblan.sys.old
The system cannot find the file specified.

C:\>


You'll notice in the above file that it renamed 1 of the drives but can't rename 2 of the drivers
I included below their location and file info


32KB System 2/26/2018
C:\Windows\System32\DriverStore\FileRepository\wdcsam.inf_amd64_7ce69fc8798d6116\wdcsam64_prewin8.sys
C:\Drivers\wdcsam.inf_amd64_7ce69fc8798d6116\wdcsam64_prewin8.sys


46KB System File 1/24/2007
C:\Program Files (x86)\Common Files\Remote Control USB Driver\usblan\wxp\fre\i386\rcblan.sys
C:\Program Files (x86)\Common Files\Remote Control USB Driver\usblan\w2k\fre\i386\rcblan.sys
C:\Windows\System32\DriverStore\FileRepository\remoteusblan.inf_amd64_f78905a23bcbcce5\amd64\rcblan.sys
C:\Program Files (x86)\Common Files\Remote Control USB Driver\usblan\wxp\fre\amd64\rcblan.sys
C:\Drivers\remoteusblan.inf_amd64_f78905a23bcbcce5\amd64\rcblan.sys


4) Rerun memory integrity > post a share link

Microsoft Windows [Version 10.0.19045.6466]
(c) Microsoft Corporation. All rights reserved.


F:\win11 upgrade failure\5-11-26\CMDs completed>hvciscan_amd64.exe
VbsGetIssues: 0x000010C0
UEFI WX Memory Attributes Table required
ACPI WSMT table required
APICV (deprecated)
VbsIsRecommended: 0
HVCI incompatible driver scan start...
HVCI: Error 1168 querying "C:\WINDOWS\System32\DriverStore\FileRepository\dddriver64dcsa.inf_amd64_3bed6326b6d247ae\dddriver64Dcsa.sys" in the SDB
HVCI: "C:\WINDOWS\System32\DriverStore\FileRepository\remoteusblan.inf_amd64_f78905a23bcbcce5\amd64\rcblan.sys" failed with compliance failure mask 00000202
HVCI: "C:\WINDOWS\System32\DriverStore\FileRepository\wdcsam.inf_amd64_7ce69fc8798d6116\wdcsam64_prewin8.sys" failed with compliance failure mask 00000202
HVCI: Error 1168 querying "C:\WINDOWS\System32\drivers\dddriver64Dcsa.sys" in the SDB
HVCI: Driver scanning complete
HVCI: scan get result failed.

F:\win11 upgrade failure\5-11-26\CMDs completed>



5) Open administrative command prompt and copy and paste:

rundll32.exe c:\windows\system32\pnpclean.dll,RunDLL_PnpClean /drivers /maxclean

Microsoft Windows [Version 10.0.19045.6466]
(c) Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>rundll32.exe c:\windows\system32\pnpclean.dll,RunDLL_PnpClean /drivers /maxclean

C:\WINDOWS\system32>


6) Reboot

Will reboot right after I post this update and then I will perform an in place upgrade repair while in clean boot

Barry

If the in place upgrade repair has not already started please run these commands:

pnputil /delete-driver oem6.inf /uninstall /force

pnputil /delete-driver oem17.inf /uninstall /force

pnputil /delete-driver oem39.inf /uninstall /force

pnputil /delete-driver oem65.inf /uninstall /force

ren C:\Windows\System32\drivers\dddriver64Dcsa.sys dddriver64Dcsa.sys.old

Post a share link.



Reboot.


Rerun memory integrity (hvciscan_amd64.exe)

Hi zbook, I checked thread after prior to starting the clean install.

Here is the output from the above commands

Microsoft Windows [Version 10.0.19045.6466]
(c) Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>pnputil /delete-driver oem6.inf /uninstall /force
Microsoft PnP Utility

Driver package uninstalled.
Failed to delete driver package: The specified file is not an installed OEM INF.

C:\WINDOWS\system32>pnputil /delete-driver oem17.inf /uninstall /force
Microsoft PnP Utility

Driver package uninstalled.
Failed to delete driver package: The specified file is not an installed OEM INF.

C:\WINDOWS\system32>pnputil /delete-driver oem39.inf /uninstall /force
Microsoft PnP Utility

Driver package uninstalled.
Driver package deleted successfully.


Will reboot for above changes to take place. And run the additional commands

C:\WINDOWS\system32>pnputil /delete-driver oem65.inf /uninstall /force
Microsoft PnP Utility

Driver package uninstalled.
Driver package deleted successfully.

C:\WINDOWS\system32>ren C:\Windows\System32\drivers\dddriver64Dcsa.sys dddriver64Dcsa.sys.old
The system cannot find the file specified.

C:\WINDOWS\system32>

Hi zbook, I think this is good news:
Microsoft Windows [Version 10.0.19045.6466]
(c) Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>f:

F:\>cd win11 upgrade failure\5-11-26\CMDs completed

F:\win11 upgrade failure\5-11-26\CMDs completed>hvciscan_amd64.exe
VbsGetIssues: 0x000010C0
UEFI WX Memory Attributes Table required
ACPI WSMT table required
APICV (deprecated)
VbsIsRecommended: 0
HVCI incompatible driver scan start...
HVCI: Driver scanning complete
HVCI incompatible driver scan passed!

F:\win11 upgrade failure\5-11-26\CMDs completed>

I will give you a little time to respond before I proceed with the clean in place upgrade

barryde said:

Microsoft Windows [Version 10.0.19045.6466

Click to expand...

Yep... that's the latest non-ESU build.
(Extended Service Updates)


Ooo... and you filled out your computer specs. Here's ten points.



If/when you do the In-Place upgrade, use Option Two (ISO method).
Use this tutorial when doing In-Place from Win 10 to Win 11.










When you finally upgrade to Win 11, here's some things that may be of use...

Hi gHot, I will start the upgrade following your recommendation in a little bit - I'm about to eat my dinner.

Thanks

The scan results look good.

Please reboot then run:

rundll32.exe c:\windows\system32\pnpclean.dll,RunDLL_PnpClean /drivers /maxclean
dir C:\Windows\System32\DriverStore\FileRepository\dddriver64dcsa*
dir C:\Windows\System32\DriverStore\FileRepository\remoteusblan*
dir C:\Windows\System32\DriverStore\FileRepository\wdcsam*

Post a share link.


Place the computer into clean boot before the in place upgrade repair using the Windows 11 iso.

Hi zbook, I saw your update after my clean win11 upgrade was started. The upgrade completed but I'm having networking issues and some kind of msconfig setting issue. I enabled the all startup items and enabled all services msconfig will not allow a "Normal Startup" selection on the general tab. If I select Normal Startup the press apply the selections change from Normal Startup to Selective Startup with a dash in the Load system services and a check in the Load startup items..

As far as the network issue, I can't connect to the internet. When running win10 I only used my ethernet cable connection and keep my wireless adapter disabled in device manager. Under win11, the wireless connects to the router and once or twice I was able to make an internet connection, but then that stopped working. I have the same issue with the ethernet adapter. I tried the troubleshooters but that didn't fix anything. I'm done working on this for today, let me know what you need from me.

I will check in an hour of two to see if you updated this.

Also did you need me to run the commands you entered in your last update

Thanks
Barry