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 only did the roll back yesterday following the instructions on this forum so dont know if it will reinstall. Am very inexperienced in computers so cant give advice.
Thank you for your comments. I did not download the utility, but, I did now. Since I rolled back the driver the utility didn't find anything assuming I'm using it correctly. What concerns me is this driver has a habit of self installing so I'm unsure as to how properly use this utility. Could you provide a sequence of events to properly use this utility. I'm assuming the driver has to installed first in order to hide it. Is that correct? Thanks
This is the first time I've used this utility, and I'm no expert. I assume that the utility must be run when the system is in a state such that Windows Update wants to install this particular driver. I.e, if you were to run Windows Update, this driver would be ready to be downloaded and installed. If not, I don't think this utility will know about the update.
So, given that, you simply need to run the utility, allow it to go through the "Detecting Problems" phase, and then you select "Hide Updates". If the driver update is listed, select it, and hide it. You can then go back to Windows Update, and this update will no longer show up, and won't be installed.
If you're happy just to pause ALL updates for a while though, there's no need to run this utility. That's what I would have done, if I had not discovered the utility.
Thank you for your comments. I did not download the utility, but, I did now. Since I rolled back the driver the utility didn't find anything assuming I'm using it correctly. What concerns me is this driver has a habit of self installing so I'm unsure as to how properly use this utility. Could you provide a sequence of events to properly use this utility. I'm assuming the driver has to installed first in order to hide it. Is that correct? Thanks
