Can not update to Build 19582 by "lsi adapter sas 3000 series 8-port with 1068" error on VMware!

Hello Kazuhiro,

Have not got around to doing the upgrade in VMware yet to build 19852, a total clean install in VMware installed with no issue.

Not sure if this may help regarding Known Issues from the Blog:

Some devices may experience a bugcheck (GSOD) during the reboot to install this update. If this happens, log in, schedule a time for the update to install, and then log off all user profiles before the scheduled install time. The install will then proceed as expected.

https://blogs.windows.com/windowsexperience/2020/03/12/announcing-windows-10-insider-preview-build-19582/

Thanks for comment.

I just tried to uninstall "lsi adapter sas 3000 series 8-port with 1068" from device manager and re-installed Build 19582.

It sucessfully installed without any error, but "lsi adapter sas 3000 series 8-port with 1068" appeared again.

And new Vmware "VMware-player-15.5.2-15785246" has been released, and so I will try to install the new Vmware and confirm this error is not occured using backup (Build 19577).

Can confim this issue. This is what I got using an ISO image that clean installed with no issue but attempting an upgrade from build 19577:

Edit:  As you mentioned, removing the Adapter in device manager allowed the upgrade to continue.

I wonder if they built-in this detection due to the issues that we were having with prior builds and SCSI adapters with VMware. Since build 19582 clean-installed without issue for you (and I presume detected the identical hardware) this seems like an unnecessary upgrade block.

Did the clean-install use the same driver as you have on build 19577 prior to the upgrade attempt?

I wonder if they built-in this detection due to the issues that we were having with prior builds and SCSI adapters with VMware. Since build 19582 clean-installed without issue for you (and I presume detected the identical hardware) this seems like an unnecessary upgrade block.

Did the clean-install use the same driver as you have on build 19577 prior to the upgrade attempt?

There would be no driver doing a clean install, booting from ISO image and deleting all partitions. (No Tools)

I updated my post in main thread Build 19582 Live showing finished upgrade with no compatibility issue in device manager. Eddie (MSFT) is looking into it. 

Basically Don, on upgrade you remove this adapter, it will request a reboot. Do not reboot as adapter will get re-installed.

Edit: Since I have to update VMware Workstation today, will try upgrade from Release build offline later today to see if I get the same result. Got to head out and see if I can find toilet paper  :-)

But a clean-install would detect the SAS hardware and then install a driver, either built-in to Windows 10 image, or via Windows Update, would it not?

Thought about that after I posted, you are correct, maybe I edit that line. Why it is triggering a block when there is no compatibility issue is beyond me.

I am assuming Kazuhiro used WU so the block didn't show up till 100% point, and whether he would have got the block screen as I did doing upgrade via ISO.

Slightly OT, but my test laptop did get the GSOD on first boot but the upgrade continued and did install. Got a second GSOD after install completed, I did not have to logout. Ran stable after that.

Edit: Curious if the driver would be included in the ISO image, we can rule out WU as I normally clean-install offline.

Running a total clean-install once more, might be installed by VMware tools, keep you posted. It is installed in the image.

I get this issue with build 15-5-2