Forum Discussion

Joerg_Debus's avatar
Joerg_Debus
Brass Contributor
Mar 09, 2022

Cannot upgrade a W10 box to W11 with Samsung SSD 980 and SQL Server 2016 installed. UPDATE.

Angelina2552 Hi, my W10 box (21H2 with all Updates) is ranked "Ready for W11" by Health Check (See below (00) ...) but no offering for an upgrade received yet from WUS.   After downloading the Se...
  • Angelina2552's avatar
    Angelina2552
    Mar 09, 2022
    Hello Joerg!

    This is Angelina. Thank you so much for reaching out regarding this matter. I will try to reach out and see if I can get some help getting this issue resolved.

    One thing I would like to suggest is attempting to install Windows 11 via a USB bootable media using the Windows 11 Media Creation Tool. (https://www.microsoft.com/software-download/windows11)
    This may allow you to install Windows 11, but I am not entirely sure as I have not encountered this problem before.
Angelina2552's avatar
Angelina2552
Copper Contributor
Mar 09, 2022
Hello Joerg!

This is Angelina. Thank you so much for reaching out regarding this matter. I will try to reach out and see if I can get some help getting this issue resolved.

One thing I would like to suggest is attempting to install Windows 11 via a USB bootable media using the Windows 11 Media Creation Tool. (https://www.microsoft.com/software-download/windows11)
This may allow you to install Windows 11, but I am not entirely sure as I have not encountered this problem before.
Joerg_Debus's avatar
Joerg_Debus
Brass Contributor
Mar 11, 2022

Angelina2552 

Hi Angelina,
it's great to hear from you!

 

The problem is easily to reproduce: Clone any W10 system disk to an Samsung SSD 980, install SQL Server 2016 - 2019 and run the W11 migration assistant. Et voilà you get the message.

 

Because there is a fix for W11 which is applied via the registry (driver parameter)  it should be no problem to upgrade if SQL Server could be blocked to start up after the installation. Unfortunately I have no idea whether the service settings for SQL Server are left untouched during migration. If they would be reset to the default, a disaster might occur, if the SQL Server tries to restart its masterdb with wrong block sizes. So using tricking the upgrade with an offline installation might overcome the block but produce major problems with the data bases.

 

So the W11 migration team should update the the upgrade process with an already available fix. Which may be published as a hot fix by MS support.

 

Until now, I'm completely depending on some "Influencer", who can pinpoint the W11 Migration Team to this problem.

 

Best regards

UP

Resources