Cannot Update Windows 10 to 11 on M.2 SSD

I have Windows 10 installed on an M.2 SSD and cannot get it to update to Windows 11. The installation almost completes but then it stops and reverts back to the current windows 10 install. I'm using a Gigabyte motherboard with TMP 2.0 installed. I have tried to do the upgrade numerous times with the same results.

I'd appreciate any advice regarding how to successfully complete this installation.

Thanks!

RAL

Try the suggestions in this article https://answers.microsoft.com/en-us...allation/ebf722db-701d-460f-985f-35c4b71383e7

Thank you for your reply glasskuter. I appreciate it! I had received some other feedback that Windows 11 will not allow an upgrade of Windows 10 that is already installed on an SSD, but I'm hoping that information is incorrect. I'd hate to have to move my Windows 10 install over to a HD just so I can do the upgrade to 11 but then have to move everything back again to the SSD! That would be such a waste of time that I'm sure Microsoft must have n alternative to.

Updating Windows 10 installed on the SSD to 11 is certainly no problem. Tested...

Thanks for the confirmation, AndreTen. I appreciate it and will keep looking for a solution!

You have not filled out the specs of your computer in your forum profile. What model are your trying to install 11 on, did it pass compatibility check, and have you run setupdiag as per the article? It should lead to what made the upgrade fail.

W10 installed in UEFI mode with disk as GPT ?

I assume you're trying to do an in-situ upGRADE from 10 > 11, thus keeping all your installed programs.

Alternate option : backup all your personal data, then use Macrium Reflect to create a backup image of your current system.

Then create a Win 11 boot USB to wipe the drive and do a clean install of Win11. Re-install all your programs, and then restore your personal data.

RAL said:

I have Windows 10 installed on an M.2 SSD and cannot get it to update to Windows 11. The installation almost completes but then it stops and reverts back to the current windows 10 install. I'm using a Gigabyte motherboard with TMP 2.0 installed. I have tried to do the upgrade numerous times with the same results.

I'd appreciate any advice regarding how to successfully complete this installation.

Thanks!

RAL

Click to expand...

Have you tried usual tricks i.e. tidy up installation as much as possible.

- disable onedrive temporarily
- disable antivirus
- run sfc /scannow
- run chkdsk c:
Then run disk cleanup

then try upgrade.

Also to do upgrade, download MS iso, mount it as a drive and run setup.exe.

This is most reliable way to upgrade.

Hello everyone. Thank you all for your assistance with this problem! Below are answers to your questions. Any other feedback would be welcome. Thanks!

AndreTen

• My system does pass the Windows 11 compatibility test.
• The error message that I get after trying to install is 0XC1900101 - 0x4001E, The installation failed in the SECOND_BOOT phase with an error during PRE_OOBE operation.
• The results of running setupdiag are:
  
  Matching Profile found: DebugSetupCrash - CEEBA202-6F04-4BC3-84B8-7B99AED924B1SetupDiag version: 1.6.2107.27002
  System Information:
  Machine Name = GIGABYTE
  Manufacturer = Gigabyte Technology Co., Ltd.
  Model = X570 AORUS PRO WIFI
  HostOSArchitecture = x64
  FirmwareType = UEFI
  BiosReleaseDate = 20220216000000.000000+000
  BiosVendor = F36a
  BiosVersion = F36a
  HostOSVersion =
  HostOSBuildString = 19041.1.amd64fre.vb_release.191206-1406
  TargetOSBuildString = 10.0.22000.194 (co_release_svc_prod1.210911-1543)
  HostOSLanguageId =
  HostOSEdition = Core
  RegisteredAV = Windows Defender
  FilterDrivers = FileInfo
  UpgradeStartTime = 2022-04-11 12:03:49 PM
  UpgradeEndTime = 2022-04-11 12:31:47 PM
  UpgradeElapsedTime = 00:27:58
  CV =
  ReportId =
  
  DebugSetupCrash
  Found qualifying memory dump during setup, but the debugger binaries were not found. Either examine the memory dump here: C:\Windows\Panther\NewOS\Panther\mnd9334.diagerr.mdmp or install the debugger tools from here: Debugging Tools for Windows (WinDbg, KD, CDB, NTSD) - Windows drivers to determine the failure.
  
  Last Setup Phase:
  Phase Name: Pre OOBE
  Phase Started: 2022-04-11 12:31:47 PM
  Phase Ended: 0001-01-01 12:00:00 AM
  Phase Time Delta: 00:00:00
  Completed Successfully? False
  
  
  Last Setup Operation:
  Operation Name: Execute provisioning migration
  Operation Started: 2022-04-11 12:31:47 PM
  Operation Ended: 0001-01-01 12:00:00 AM
  Operation Time Delta: 0:00:00:00.0000000
  Completed Successfully? False
  
  
• Prior to running this most recent installation attempt, I uninstalled Norton 360, ran sfc /scannow and updated my bios.
• Here are my system specs:
  
  Edition Windows 10 HomeVersion 21H2
  Installed on ‎2021-‎08-‎04
  OS build 19044.1586
  Experience Windows Feature Experience Pack 120.2212.4170.0
  
  Device name GIGABYTEProcessor AMD Ryzen 9 3900X 12-Core Processor 3.80 GHz
  Installed RAM 64.0 GB
  Device ID 37EC732E-B183-4316-AAD6-D071C3095947
  Product ID 00326-10000-00000-AA885
  System type 64-bit operating system, x64-based processor
  Pen and touch No pen or touch input is available for this display
  

CountMike

Windows 10 is installed on the M.2 SSD in GPT mode. Thanks for comment and having me look into that.

idgat

Yes, I'm trying not to have to start from scratch and reload all of my applications again, but if all else fails, your suggestion will be the best next solution. Thanks!

cerebreus

I've tried everything on your list except disabling onedrive and running disk cleanup (which I'll try now). I am trying to install Windows 11 from a Microsoft ISO file as suggested. Thanks for your great input!

Please run and post share links into this thread using one drive, drop box, or google drive:

a) Tuneup plus: https://www.tenforums.com/attachmen...-files-use-bsod-debugging-tuneup_plus_log.bat

b) Events: https://www.tenforums.com/attachmen...collect_logs_from_event_viewer-2021-09-14.bat

c) V2: BSOD - Posting Instructions

d) Dump files: Gather_additional_dump_files.bat ─ Click here to go to the BSOD batch repository to download and run this batch file.

Hey, glasskuter. In my last post, I meant to respond to your inquiry, but labeled my response to AndreTen instead. Sorry!

The log collectors / scripts are likely to collect many of the important files.

To make sure that this file is collected please search for:
C:\Windows\Panther\NewOS\Panther\mnd9334.diagerr.mdmp

and post a share link using one drive, drop box, or google drive.

You know what, I had exactly the same problem with the PC I recently built for my daughter (R7 3700x on Gigabyte B550M DS3H motherboard, XPG Spectrix M.2 SSD). I specifically built it for Windows 11 and I did an in-place upgrade with an ISO.
I tried 3x late last year to early this year with the same result as yours... BSOD after the first boot. And then revert back 10. I did not really pay attention to what the problem was and just did not keep trying until last weekend which finally went through without a problem. I did not do anything to resolve the problem. I just tried again and I was ready to dig through the issue but it just went through smoothly this time.
The only thing I have in mind that fixes the issue is probably the latest update that addresses the same issue other people were experiencing. I really don't know what to tell you to help resolve the problem. I am just sharing the same experience I had which I did not try to fix but it fixed itself in time.

RAL said:

Sorry!

Click to expand...

No problem. I know clean install is a pain, but you won't regret it in the long run. I do it every time instead of an upgrade. A lot of folks here disagree with my thinking and have upgraded multiple times over one installation. But I'm kind of old school and a stickler for doing everything I can to guarantee that no junk carries over. I know that Windows can be a fickle bee-itch and don't want her to come back and bite me in the behind.

It's opposite in my case. This W11 hails from W7.
So when W8 came out (still as Beta), I upgraded to it and than to it and consequently to W8.1. When W10 came out, upgrade from 8.1 went poorly (mostly driver problems) so I installed W7 again and upgraded to W10.
Installed unofficial W11 on another disk and kept it in dual boot until official W11 release with which I upgraded W10. There were even some radical hardware changes. From FX 6350 system which held W7, W/8.1 and early W10, transferred to first Ryzen system which itself had several upgrades (4 CPUs, 2 MBs, 3 RAM changes, 2 GPUs and several disks including changes from SATA SSDs to NVMe (twice). Transfers were always done using Macrium Reflect backups.
I have so much SW installed, spread over 3 disks so it would take me at least a week for a clean install and considering all licenses and passwords, maybe even longer with uncertain results. I do very comprehensive and regular backups and I'm conteplating clean install for a while but putting it off because of those complications. So while everything is working perfectly I don't think it will be soon.

As an update to this thread, please note that I tried removing all external devices from my system (except for the keyboard and mouse) and attempted to install Windows 11. Unfortunately, it didn't work and has the same error message 0XC1900101 - 0x4001E, The installation failed in the SECOND_BOOT phase with an error during PRE_OOBE operation.

Cereberus, regarding your suggestion of doing a clean install of Windows 11 onto the SSD, I'm wondering, if a clean install removes Windows 10 do I then need a new activation key for Windows 11 to install correctly?

Also, thank you Badrobot for your feedback! Unfortunately, even though I'm completely updated, I haven't had the same luck that you have with completing this install. I'm glad you're up and running though!

RAL said:

As an update to this thread, please note that I tried removing all external devices from my system (except for the keyboard and mouse) and attempted to install Windows 11. Unfortunately, it didn't work and has the same error message 0XC1900101 - 0x4001E, The installation failed in the SECOND_BOOT phase with an error during PRE_OOBE operation.

Cereberus, regarding your suggestion of doing a clean install of Windows 11 onto the SSD, I'm wondering, if a clean install removes Windows 10 do I then need a new activation key for Windows 11 to install correctly?

Also, thank you Badrobot for your feedback! Unfortunately, even though I'm completely updated, I haven't had the same luck that you have with completing this install. I'm glad you're up and running though!

Click to expand...

License is tied to motherboard so if W10 was activated W11 will activate as soon as it reaches MS server. Even easier if you have an MS account.

Thank you for your posts, Zbook. I'm not sure if I understand properly what you're asking me to do, but here are the results when I ran the windows debugger tool on the .mdmp file generated after my most recent install attempt:


Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Panther\NewOs\Panther\mnd6F32.diagerr.mdmp]
User Mini Dump File: Only registers, stack and portions of memory are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Version 22000 MP (24 procs) Free x64
Product: WinNt, suite: SingleUserTS Personal
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Debug session time: Mon Apr 11 15:11:39.000 2022 (UTC - 4:00)
System Uptime: not available
Process Uptime: 0 days 0:01:22.000
................................................................
..........................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(7e0.7e4): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtGetContextThread+0x14:
00007ffc`97125234 c3 ret
0:000> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

Failed to request MethodData, not in JIT code range

KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Write

Key : Analysis.CPU.mSec
Value: 12296

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 12298

Key : Analysis.Init.CPU.mSec
Value: 124

Key : Analysis.Init.Elapsed.mSec
Value: 54271

Key : Analysis.Memory.CommitPeak.Mb
Value: 247

Key : CLR.BuiltBy
Value: NET48REL1LAST_C

Key : CLR.Engine
Value: CLR

Key : CLR.Version
Value: 4.8.4400.0

Key : Timeline.Process.Start.DeltaSec
Value: 82

Key : WER.OS.Branch
Value: co_release

Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z

Key : WER.OS.Version
Value: 10.0.22000.1

Key : WER.Process.Version
Value: 1.66.22000.1


FILE_IN_CAB: mnd6F32.diagerr.mdmp

CONTEXT: (.ecxr)
rax=00000000ffffffff rbx=00000164b4fa3498 rcx=68977829cf440000
rdx=0000000000000001 rsi=00000164bd1b12a0 rdi=0000000000000000
rip=00007ffc79a9b93e rsp=000000267327a1b0 rbp=000000267327a520
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000246 r12=00000164b4ef1800 r13=0000000000000000
r14=00000164b4ef17f0 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246
MdmDiagnostics!Microsoft::Windows::Mdm::MdmDiagnosticSource:olicyDiagDataSource::AddRedirectedOrGroupPolicyValues+0x652:
00007ffc`79a9b93e 66893c43 mov word ptr [rbx+rax*2],di ds:00000166`b4fa3496=????
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffc79a9b93e (MdmDiagnostics!Microsoft::Windows::Mdm::MdmDiagnosticSource:olicyDiagDataSource::AddRedirectedOrGroupPolicyValues+0x0000000000000652)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 00000166b4fa3496
Attempt to write to address 00000166b4fa3496

PROCESS_NAME: SetupPlatform.exe

WRITE_ADDRESS: 00000166b4fa3496

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 00000166b4fa3496

STACK_TEXT:
00000026`7327a1b0 00007ffc`79a9bc3b : 00000164`bd1b12a0 00000164`bd1b12a0 00000164`bd9c4cb8 00000164`bd9c4cb8 : MdmDiagnostics!Microsoft::Windows::Mdm::MdmDiagnosticSource:olicyDiagDataSource::AddRedirectedOrGroupPolicyValues+0x652
00000026`7327a4a0 00007ffc`79a9bf50 : 00000000`00000000 00000026`0000000f 00000164`b58f5010 00000164`be9cd738 : MdmDiagnostics!Microsoft::Windows::Mdm::MdmDiagnosticSource:olicyDiagDataSource::RetrieveRedirectedRegKeyData+0xeb
00000026`7327a4e0 00007ffc`79a9c188 : 00000164`b66fa370 00000164`bd1b12a0 00000000`00000000 00000164`bd1b3f88 : MdmDiagnostics!Microsoft::Windows::Mdm::MdmDiagnosticSource:olicyDiagDataSource::InsertRedirectedRegKeyData+0x218
00000026`7327a540 00007ffc`79a88180 : 00007ffc`79a9a4c0 00000000`00000001 00007ffc`79a9c090 00000000`00000001 : MdmDiagnostics!Microsoft::Windows::Mdm::MdmDiagnosticSource:olicyDiagDataSource::GetDiagnosticData+0xf8
00000026`7327a5e0 00007ffc`79a8c43c : 00000026`7327a8e0 00000026`7327a8e0 00000000`00000000 00000164`bde4c4d0 : MdmDiagnostics!CreateMdmEnterpriseDiagnosticReport+0x3b30
00000026`7327a810 00007ffc`79a8d36f : 006f0072`00630069 00740066`006f0073 00610069`0044005c 0073006f`006e0067 : MdmDiagnostics!CreateLogOnAreaInternal+0xa5c
00000026`7327ab80 00007ffc`883c0ff8 : 00007ffc`883e8110 00000164`b80361c0 ffffffff`ffffffff 00000000`00000000 : MdmDiagnostics!CreateLogCabOnArea+0xf
00000026`7327abb0 00007ffc`883c0f1f : 00000026`7327ace8 00000026`7327ac40 00000000`00000000 00000000`00000000 : provops!ProvOperations:ublishDeviceProvisioningLogs+0x18
00000026`7327abe0 00007ffc`883c0cf6 : 00000164`b3880f00 00000164`b3880f00 00000000`000000b7 00007ffc`883e53a0 : provops!<lambda_efbde755ed85fba1fb214dc514d534cb>:perator()+0xe7
00000026`7327ac50 00007ffc`88fc5380 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : provops!ProvOperations::ApplyKnownPackages+0xa46
00000026`7327b210 00007ffc`89ee33b2 : 00000164`ba6e6658 00000164`b1e2f6d8 00000026`7327b570 00000164`b1e2f6d8 : ProvMigrate!ProvMigration+0x290
00000026`7327b2d0 00007ffc`8a037e93 : 00000164`ba6e6658 00000164`b1e2f6d8 00000000`00000006 00000000`00000000 : SetupPlatform!CProvisioningMigration:oExecute+0x252
00000026`7327b370 00007ffc`8a042596 : 00000164`b1e2f6d8 00000021`0000000a 01d84db6`8000ffff 01d8f1a5`013b7000 : SetupPlatform!COperation::Execute+0x1ab
00000026`7327b470 00007ffc`8a04519b : 00000164`b1da6d88 00000164`be6f2548 00007ffc`0000000a 00000000`00000002 : SetupPlatform!COperationQueue::ExecuteOperationsInternal+0x1d12
00000026`7327b7a0 00007ffc`89f0d6c9 : 00000000`00000000 00000026`7327b8d0 00000164`be6f2548 00000000`00000000 : SetupPlatform!COperationQueue::ExecuteOperations+0x1ef
00000026`7327b850 00007ffc`89f16c97 : 00000164`b1de9ab8 00000000`00000000 00000164`b1de9ba8 00000000`00000000 : SetupPlatform!pExecutePostBootOperations+0x2e1
00000026`7327b930 00007ff6`ea0d3bec : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : SetupPlatform!CSetupPlatformPrivate::Execute+0x6857
00000026`7327c770 00007ff6`ea0da74d : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00000000 : SetupPlatform_exe!wWinMain+0x229c
00000026`7327fe50 00007ffc`959a54e0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : SetupPlatform_exe!__wmainCRTStartup+0x1dd
00000026`7327ff10 00007ffc`9708485b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x10
00000026`7327ff40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x2b


STACK_COMMAND: ~0s; .ecxr ; kb

SYMBOL_NAME: MdmDiagnostics!Microsoft::Windows::Mdm::MdmDiagnosticSource:olicyDiagDataSource::AddRedirectedOrGroupPolicyValues+652

MODULE_NAME: MdmDiagnostics

IMAGE_NAME: MdmDiagnostics.dll

FAILURE_BUCKET_ID: INVALID_POINTER_WRITE_c0000005_MdmDiagnostics.dll!Microsoft::Windows::Mdm::MdmDiagnosticSource:olicyDiagDataSource::AddRedirectedOrGroupPolicyValues

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 10.0.22000.282

FAILURE_ID_HASH: {f0714e23-f780-a684-be3f-2566c47d2ccd}

Followup: MachineOwner

Hello glasskuter. I've updated my system info in my profile, in case you needed more info,