ne with me it does not even work on original hardware without Vmware. Wanted to set up new image, friend wanted Plex server etc.. Do not get the thing to run look at me tomorrow times, already too late, watch now film. Sleep all good
same BSOD for me on the latest VMware Workstation when setup is trying to create new partitions my disk drive was NVMe by default, I've deleted it and added new SATA one, now it installs without any BSOD maybe latest updates breaks NVMe compatibility for x86 systems
september is fine (19045.2006) Spoiler: list of updates Code: 1/10: defender-dism-x86_18.11.2022.cab 2/10: windows10.0-kb5007401-x86_DU.Critical_1378.1.1.cab 3/10: windows10.0-kb5011048-x86_ndp481_8028.cab [NetFx] 4/10: windows10.0-KB5011577-x86_DU.SafeOS_1616.1.1.cab [SafeOS DU] 5/10: windows10.0-kb5012170-x86_DBX_1880.1.1.cab [SecureBoot] 6/10: windows10.0-kb5015684-x86_EP.22H2_1799.1.2.cab [Enablement] 7/10: windows10.0-KB5016705-x86_SSU_1940.1.0.cab [SSU] 8/10: windows10.0-kb5016775-x86_DU.Sources_1940.cab [Setup DU] 9/10: windows10.0-kb5017308-x86_LCU_2006.1.7.cab [LCU] 10/10: windows10.0-kb5020623-x86-ndp481_CU_9110.7.cab [NetFx] I'll try to test newer updates, but it takes time and there were so many out-of-band updates lately
october LCU (19045.2130) is incompatible with NVMe drives Spoiler: List of updates Code: 1/10: defender-dism-x86_18.11.2022.cab 2/10: windows10.0-kb5007401-x86_DU.Critical_1378.1.1.cab 3/10: windows10.0-kb5011048-x86_ndp481_8028.cab [NetFx] 4/10: windows10.0-KB5011577-x86_DU.SafeOS_1616.1.1.cab [SafeOS DU] 5/10: windows10.0-kb5012170-x86_DBX_1880.1.1.cab [SecureBoot] 6/10: windows10.0-kb5015684-x86_EP.22H2_1799.1.2.cab [Enablement] 7/10: windows10.0-KB5016705-x86_SSU_1940.1.0.cab [SSU] 8/10: windows10.0-kb5018410-x86_LCU_2130.1.9.cab [LCU] 9/10: windows10.0-kb5019420-x86_DU.Sources_2127.cab [Setup DU] 10/10: windows10.0-kb5020623-x86-ndp481_CU_9110.7.cab [NetFx] BSOD to stornvme.sys going to test 19045.2075 next edit: 19045.2075 is incompatible too Spoiler: List of updates Code: 1/10: defender-dism-x86_18.11.2022.cab 2/10: windows10.0-kb5007401-x86_DU.Critical_1378.1.1.cab 3/10: windows10.0-kb5011048-x86_ndp481_8028.cab [NetFx] 4/10: windows10.0-KB5011577-x86_DU.SafeOS_1616.1.1.cab [SafeOS DU] 5/10: windows10.0-kb5012170-x86_DBX_1880.1.1.cab [SecureBoot] 6/10: windows10.0-kb5015684-x86_EP.22H2_1799.1.2.cab [Enablement] 7/10: windows10.0-KB5016705-x86_SSU_1940.1.0.cab [SSU] 8/10: windows10.0-kb5017380-x86_LCU_2075.1.13.cab [LCU] 9/10: windows10.0-kb5017404-x86_DU.Sources_2060.cab [Setup DU] 10/10: windows10.0-kb5020623-x86-ndp481_CU_9110.7.cab [NetFx] so it's started from 2075 LCU or KB5017404 going to test it again with KB5016775 edit: no luck, this is because of LCU I'm going to build boot.wim with KB5017308 (+latest SSU), I think this combo of old boot.wim + latest ISO should work edit: yep, works fine with outdated boot.wim during setup stage but BSOD after reboot not sure if it's even working on NVMe drives on old OSes with updates installed online, will try it tomorrow so far only 19045.2006 is working for me edit: so.. I've installed 19045.2006 without internet and vmware tools, installed latest LCU online and got BSOD bootloop the same BSOD bootloop with vmware tools preinstalled
can't manage partitions in UEFI and BIOS modes on 17763.3653 it just can't create new one or delete something, but no BSOD this time Spoiler: List of updates defender-dism-x86_25.11.2022.cab windows10.0-kb4486153-x86_ndp48_3106.cab windows10.0-kb5005545-x86_DU.Sources_2111.cab windows10.0-kb5012170-x86_DBX_3280.1.1.cab windows10.0-kb5020374-x86_SSU_3641.1.1.cab windows10.0-kb5020615-x86-ndp48_CU_4585.2.cab windows10.0-kb5021042-x86_DU.SafeOS_3646.1.0.cab windows10.0-kb5021655-x86_LCU_3653.1.3.cab also works fine on SATA drive
This sounds like your nvme is having issues. Mine (Sandisk) started like that until it was no longer possible to write anything on it. I didn't lose the data, but it got stuck in read-only. Test some linux distro on liveusb to check if reading, writing and editing table and partitions is ok. Recommend SparkyLinux Recue Edition
no, this is VMware Workstation NVMe drive, latest Windows 10 x86 builds are incompatible with all NVMe drives
I don't have any NVMe drives because my MB is too old I think real hardware is affected too because KleineZiege can't install it I'll see if VirtualBox is affected and update this post tomorrow, no idea if it's even has NVMe drive type support
Dear @abbodi1406, I've been using your Windows 10 1809 batch script, AMAZING! Do you have one for Windows 11 (hopefully that skips defender too)? You are a legend my friend!
You mean this? https://forums.mydigitallife.net/goto/post?id=1566032#post-1566032 https://forums.mydigitallife.net/goto/post?id=1742386#post-1742386 i have updated one for Win11 (22000), but i only tested it twice and there was some hiccups https://box.com/index.php?rm=box_do...wl444zhvr1ii07dz0w023&file_id=f_1078654660925
I can't install Windows in VirtualBox on NVMe drive, setup just can't find any HDD drive I think I need NVMe controller drivers for V-Box but I have no idea where to get it, I've tried to find it on V-Box tools ISO but it's not there either I guess NVMe controller is not for boot drive there
Could these issues be related to RAID vs AHCI on the host PC with an NVMe boot drive? I had Disk Imaging issues with my Dell XPS Laptops which defaulted to RAID, I don't use or need RAID, so switched to AHCI and have had no compatibility issues since...