It turns out RAID was causing the problem as it was trying to download drivers that were not compatible with my Omen 30L. I disabled it in the BIOS and switched to AHCI instead. Problem solved.
I'm puzzled how Microsoft convinced the PC builders to force install drivers on their systems. Some on this forum have reported ruined motherboards because of Microsoft's Windows Updater.
I think the cause is related to disk-signatures and the fact that Windows is not going to allow identical installations of Windows to co-exist in the same system.
People often run into this when cloning (poorly or with random procedures).
I think what it comes down to is the prior disk can not be re-introduced into the system until it is Diskpart-cleaned (sometimes on a separate system). I often just boot and do that with a Macrium Reflect Rescue Drive or a Windows Installer flash-drive.
In retrospect, I think I would have just installed MSFS on 1-tb NVMe C-Drive. Or, maybe bought another for D-Drive. The 256gb-SSD is not really big enough for most peoples C-Drive (now-days 480gb is minimum) as you want it to hold all Windows, and all apps/programs.
I'm puzzled how Microsoft convinced the PC builders to force install drivers on their systems. Some on this forum have reported ruined motherboards because of Microsoft's Windows Updater.
Think of Surface Tablets (and Surface Laptop). I think they want everything to online update like a mobile-phone, iPad, your TV ... well, basically everything now-days.
I see and understand your point and it's well taken and it makes a lot of sense, when it is your product, your hardware. The problem becomes, when it is NOT your product or hardware but you are only involved by means of your software. It created a ton of problems for me by making my system totally unstable, because they forced drivers that were not compatible with my hardware. That's where things tend to get wonky.
A month ago when Dell had their liquidation sale going on the R10's, I bought one on a huge discount. I wanted an all AMD setup with either a 6800 XT or 6900 XT. I forgot to disable the Windows BIOS setting and Windows 11 installed a new BIOS and blew out the motherboard. I tried every trick mentioned in this forum. I tried to reorder one but they were OOS.
That's my problem with Microsoft since Windows 10. Prior to that, you could pick and choose what drivers you wanted installed. Now, that is no longer an option unless you buy Windows Enterprise Edition. There are ways around it but that involves 3rd party software to override Windows Update and disabling WU.
I don't believe the issue lies with Microsoft. Anything on Windows update has to be submitted. So if a driver or BIOS update fails and bricks a motherboard, that's on the Company that submitted the files to Microsoft, for not testing them properly prior to release.
And that is a valid point you made. However, if the enduser would be allowed to install system drivers at their discretion then it would cause less problems in the long run for someone beyond novice abilities. I remember a situation in the past where an Nvidia WQHL driver caused the GPU to intermittently shut off the fans on the videocard.
I understand security updates but wholesale drivers should be allowed at the end users discretion or at the very least give that person the option. We can do that for you automatically or you the end user can take over.
I can count many times in the last 15-20 years where some certified drivers caused problems or were a downgrade in performance.
On this forum it is widely accepted that if your PC is stable, you might not want to upgrade the BIOS unless it fixes a problem you are experiencing. With Microsoft's approach those rules don't apply.
RodsterB
2 Intern
•
406 Posts
0
November 26th, 2022 13:00
It turns out RAID was causing the problem as it was trying to download drivers that were not compatible with my Omen 30L. I disabled it in the BIOS and switched to AHCI instead. Problem solved.
I'm puzzled how Microsoft convinced the PC builders to force install drivers on their systems. Some on this forum have reported ruined motherboards because of Microsoft's Windows Updater.
Tesla1856
8 Wizard
•
17.3K Posts
0
November 25th, 2022 20:00
Well, as far as the fix ... not sure.
I think the cause is related to disk-signatures and the fact that Windows is not going to allow identical installations of Windows to co-exist in the same system.
People often run into this when cloning (poorly or with random procedures).
I think what it comes down to is the prior disk can not be re-introduced into the system until it is Diskpart-cleaned (sometimes on a separate system). I often just boot and do that with a Macrium Reflect Rescue Drive or a Windows Installer flash-drive.
In retrospect, I think I would have just installed MSFS on 1-tb NVMe C-Drive. Or, maybe bought another for D-Drive. The 256gb-SSD is not really big enough for most peoples C-Drive (now-days 480gb is minimum) as you want it to hold all Windows, and all apps/programs.
Tesla1856
8 Wizard
•
17.3K Posts
0
November 26th, 2022 22:00
Think of Surface Tablets (and Surface Laptop). I think they want everything to online update like a mobile-phone, iPad, your TV ... well, basically everything now-days.
RodsterB
2 Intern
•
406 Posts
0
November 27th, 2022 04:00
I see and understand your point and it's well taken and it makes a lot of sense, when it is your product, your hardware. The problem becomes, when it is NOT your product or hardware but you are only involved by means of your software. It created a ton of problems for me by making my system totally unstable, because they forced drivers that were not compatible with my hardware. That's where things tend to get wonky.
A month ago when Dell had their liquidation sale going on the R10's, I bought one on a huge discount. I wanted an all AMD setup with either a 6800 XT or 6900 XT. I forgot to disable the Windows BIOS setting and Windows 11 installed a new BIOS and blew out the motherboard. I tried every trick mentioned in this forum. I tried to reorder one but they were OOS.
That's my problem with Microsoft since Windows 10. Prior to that, you could pick and choose what drivers you wanted installed. Now, that is no longer an option unless you buy Windows Enterprise Edition. There are ways around it but that involves 3rd party software to override Windows Update and disabling WU.
Vanadiel
6 Professor
•
7.1K Posts
0
November 27th, 2022 05:00
I don't believe the issue lies with Microsoft. Anything on Windows update has to be submitted. So if a driver or BIOS update fails and bricks a motherboard, that's on the Company that submitted the files to Microsoft, for not testing them properly prior to release.
RodsterB
2 Intern
•
406 Posts
0
November 27th, 2022 06:00
And that is a valid point you made. However, if the enduser would be allowed to install system drivers at their discretion then it would cause less problems in the long run for someone beyond novice abilities. I remember a situation in the past where an Nvidia WQHL driver caused the GPU to intermittently shut off the fans on the videocard.
I understand security updates but wholesale drivers should be allowed at the end users discretion or at the very least give that person the option. We can do that for you automatically or you the end user can take over.
I can count many times in the last 15-20 years where some certified drivers caused problems or were a downgrade in performance.
On this forum it is widely accepted that if your PC is stable, you might not want to upgrade the BIOS unless it fixes a problem you are experiencing. With Microsoft's approach those rules don't apply.