This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I rec'd an Intel SCSI Adapter update V 17.5.3.1026, this AM, thru the Windows update screen. After the install I immediately has boot up problems. The boot up would stall at the Dell logo screen and go no further. I was able to get to boot up once in a while by powering off and restarting from the power button, but that didn't work very often. When it did boot up using this method it was pretty sluggish. I contacted Dell support and they were not aware of the problem. I subsequently reviewed some Dell community forum posts and there were other people reporting the exact same problem in May 2020. I was finally able to get back to normal operating condition by doing a system point restore prior to the download. The jist of the forums was there is problem with the RST and BIOS not in sync. Both of those are current according to Dell drivers and download screen. Dell has fowarded the problem to the engineering dept for review. The next time I checked for updates the Intel showed up again but I did not install. I'm OK as long as it does not try to self install. I also contacted MS support and they wanted to update me V 2004 which I declined as it still is showing for developers. Any thoughts on what to do here? Thanks
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi,
I have experienced the same issue on my Dell XPS 8920 tower, because I was aware that an intel driver was updated before the issue. So I did a driver roll back inside device manager. And everything has back to normal now. So ABSOLUTELY no need for a system restore! just roll it back
I had the same issue with it crashing when w10 starts up or from hibernation after a windows update which is bundled with an Intel driver update and believe I've solved it.
I am no expert and cannot vouch for any side-effects but I found the newly installed Intel driver, rolled it back and now I no longer have any start-up issues.
Go to Device manager>Storage Controllers>Intel(R) Chipset SATA.....>Properties>Driver>Rollback Driver.
No more problems with start-up
I am happy to report that I have had success in getting my PC working again! On another computer I downloaded the Windows 10 May 2020 Update from the Microsoft website onto a flash drive following all the instructions for installing it on a different computer. On our slow internet this took several hours, so be patient. I powered up the problem PC after plugging in the flash drive. The computer opened to what I believe is called the Windows RE screen. Choose the Troubleshoot option and then select Repair (the repair statement is smaller at the bottom of the page). Very quickly I had my login screen back and after logging in found that all data was intact.
After the computer was running, the notifications icon was highlighted and on opening it said that Microsoft had deleted some updates that had caused a problem with the computer starting. I checked the Microsoft updates history and saw that the problem scsi download was shown as "Failed." I am not sure if the failure was the original attempt to install or reflected that Microsoft had deleted it.
I hope this may be useful for others with this problem. And, pausing updates for a while is probably still a good idea!
I would suggest that you follow the suggestion of a previous commentator and pause your W10 updates for, at least, 7 days, and perhaps someone will figure this out at MS/Intel/Dell
Your problem with booting is beyond my abilities to help. I would suggest that you contact Dell since they contributed to the problem. Perhaps they can see some way to help you without charging you. Hopefully, one of the commentators on this blog can help as well.
