This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I am looking for some help here. I have tried this so a crazy extent, to me. I have have attempted like 50 or 60 and always get the same result. Is get the error with the 1900101-40017 error. The references is a failure on the second boot. I understand from my research it is associated with devices.
I have done in place upgrades on my Windows 10 but I still get the errors.
I got some which were released to hyper-v which I disabled ans it went away.
I had another the that dealt with SCAN and I got that to go away.
What I am left with is a root/kdnic/0000 issue. I know it's not a good thing but I even went as far as deleting the Kernel Debug from the Device list under network adapters and I delete everything from the registers that had any reference to kdnic. I know that was not a wise thing to do but it didn't matter because still the same error.
I removed my machine to get it back to a state post a successful in place windows 10 upgrade.
What other steps can I do to get this resolved so I can upgrade?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Just so you know and as mentioned on another thread. I am not having any BSOD hence the reason I didn't run anything on those steps.
However, yeah, I forgot to run the V2 collector and I mentioned I would.
I did. They are in that Dropbox under the "DAVISM01-(2025-05-24_11-22-13).zip".
Ok, are they supposed to also be in the migration folder because they are not.
But outside of that they are there in the C:\Mount\Windows\System32, yet it does not show the bit version and I did the 64-bit in the Media Tool, I know that.
It is interesting because they are there on the Windows 10 machine.
"C:\WINDOWS\system32>dir C:\Windows\System32\CscMig.dll
Volume in drive C has no label.
Volume Serial Number is EC21-E039
Directory of C:\Windows\System32
05/22/2025 21:16 146,848 CscMig.dll
1 File(s) 146,848 bytes
0 Dir(s) 443,416,444,928 bytes free
C:\WINDOWS\system32>dir C:\Windows\System32\WSManMigrationPlugin.dll
Volume in drive C has no label.
Volume Serial Number is EC21-E039
Directory of C:\Windows\System32
12/03/2023 20:46 88,576 WSManMigrationPlugin.dll
1 File(s) 88,576 bytes
0 Dir(s) 443,416,444,928 bytes free"
But if they are using it from the Win11 ISO, I created that ISO from the Windows 11 Media Kit.
Now this is weird too...
"F:\sources>dism /Get-WimInfo /ImageFile:"F:\sources\install.esd"
Deployment Image Servicing and Management tool
Version: 10.0.26100.1
Error: 87
The /imagefile option is not recognized in this context.
For more information, refer to the help.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
F:\sources>dir install.esd
Volume in drive F is WIN11ENT
Volume Serial Number is 0007-3258
Directory of F:\sources
05/23/2025 20:10 4,066,092,418 install.esd
1 File(s) 4,066,092,418 bytes
0 Dir(s) 26,409,058,304 bytes free
" and as you see it is right there but yet DISM is not recognizing it.
DISM.LOG
"2025-05-24 10:46:27, Info DISM PID=104484 TID=102148 Scratch directory set to 'C:\Users\Marc\AppData\Local\Temp'. - CDISMManager::put_ScratchDir
2025-05-24 10:46:27, Info DISM PID=104484 TID=102148 DismCore.dll version: 10.0.26100.1 - CDISMManager::FinalConstruct
2025-05-24 10:46:27, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2025-05-24 10:46:27, Info DISM PID=104484 TID=102148 Successfully loaded the ImageSession at "F:\sources" - CDISMManager::LoadLocalImageSession
2025-05-24 10:46:27, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2025-05-24 10:46:27, Info DISM DISM Provider Store: PID=104484 TID=102148 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2025-05-24 10:46:27, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2025-05-24 10:46:27, Info DISM DISM Manager: PID=104484 TID=102148 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2025-05-24 10:46:27, Info DISM DISM.EXE:
2025-05-24 10:46:27, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
2025-05-24 10:46:27, Info DISM DISM.EXE:
2025-05-24 10:46:27, Info DISM DISM.EXE: Host machine information: OS Version=10.0.19045, Running architecture=amd64, Number of processors=32
2025-05-24 10:46:27, Info DISM DISM.EXE: Instance information: Parent process=C:\WINDOWS\System32\cmd.exe, Parent process PID=101748
2025-05-24 10:46:27, Info DISM DISM.EXE: Dism.exe version: 10.0.26100.1
2025-05-24 10:46:27, Info DISM DISM.EXE: Executing command line: dism /Get-WimInfo /ImageFile:"F:\sources\install.esd"
2025-05-24 10:46:27, Error DISM DISM WIM Provider: PID=104484 TID=102148 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:2483 - CWimManager::InternalValidateOptions(hr:0x80070057)
2025-05-24 10:46:27, Error DISM DISM WIM Provider: PID=104484 TID=102148 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:2314 - CWimManager::ExecuteCmdLine(hr:0x80070057)
2025-05-24 10:46:27, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2025-05-24 10:46:27, Info DISM DISM.EXE:
2025-05-24 10:46:27, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2025-05-24 10:46:27, Info DISM DISM.EXE: "
"UPDATE: This worked. Now, I can do the rest with the index.
dism /Get-WimInfo /WimFile:f:\sources\install.esd"
Thanks. The errors in your setupact.log show that Setup successfully loaded the ContextMigration plugin from
$WINDOWS.~BT\NewOS\Windows\system32\migration\CntrtextMig.dll
but repeatedly failed to load both WSManMigrationPlugin.dll and CscMig.dll from $WINDOWS.~BT\NewOS\Windows\system32\… each time returning module-not-found (0x7f). In a proper Windows 11 install image those two DLLs live alongside the rest of the migration plugins (under system32 and the migration folder). What that tells us is your ISO/WIM doesn't contain them in the right place or at the right bitness. Stop your upgrade attempt and do this next. Mount your Windows 11 install.wim (or .esd) on your Windows 10 machine, point DISM at it and verify the files are present before you retry. Open an elevated prompt and run:
dism /Get-WimInfo /ImageFile:"D:\sources\install.wim"
(Adjust the path to where your ISO is mounted and the index number if you're using Enterprise, Home, etc.)
Then mount that same index:
mkdir C:\Mount
dism /Mount-Wim /WimFile:"D:\sources\install.wim" /Index:1 /MountDir:C:\Mount
Once it's mounted, browse to C:\Mount\Windows\System32 and confirm you see WSManMigrationPlugin.dll and CscMig.dll, and under C:\Mount\Windows\System32\migration you see the usual set of MIG DLLs besides the Context one. If those two DLLs are missing or are 32-bit only (you can right-click Properties > Details tab to see the file version and architecture), your image is bad.
If they're missing or wrong, discard that ISO and grab the official Windows 11 ISO directly from the Media Creation Tool. Mount the fresh ISO, repeat the DISM check, and only then rerun setup from inside Windows 10 (still fully offline and with all extraneous devices unplugged and Hyper-V disabled).
Once you've validated the media and you still see the 1900101-40017 rollback, come back with the new setupact.log. If the two migration DLLs are present, we'll look next at repairing your Windows 10 component store before a final upgrade pass.
The requested log files in the first post were missing from the recent share link.
How come you were unable to run V2 and were able to run FRST?
The other script results had similar file results.
For troubleshooting the BSODs:
BSOD - Posting Instructions - Windows 10 Forums
Create System Restore Point in Windows 10 | Tutorials
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
Boot to Advanced Startup Options in Windows 10 | Tutorials
and run one or more of these commands:
verifier /reset
verifier /bootmode resetonbootfail
verifier /querysettings
Post a share link.