Sheldon hit the nail on the head with this one, as regards the Intel Rapid Storage Drivers. I just did a clean install of Windows 7 Professional (Dell OEM, in this case) and (thinking I was doing everything right) downloaded all the
latest Intel drivers straight from their Website, installed them in the recommended order (so there were no yellow "bangs" in Device Manager - everything there looked perfect) and then tried to run Windows Update to finish-off the
job when I hit the brick wall described above. You will note that I had the latest drivers installed and that didn't fix the problem, so I suspect even if you have an older version on your computer, simply updating them may still do nothing to help. In analyzing
what could have gone wrong with a "clean install" this early in the game, Sheldon's advice about the Intel Rapid Storage drivers stuck out like a sore thumb and made perfect sense; very seldom could something else have become corrupted this early-on in the
process. Had I been able to identify the individual drivers in Device Manager I would have opted to simply disable them temporarily but I couldn't be sure of which were which, so I just uninstalled the entire Intel program in question, rebooted and Windows
Update ran immediately with no problem whatsoever. I then reinstalled the Rapid Storage drivers and went on my merry way.
Now as to why Intel, knowing this to be a problem for this many months (apparently it happens consistently) has let this go on so long without fixing it is anybody's guess. Anybody who is anywhere near being a "power user" is always going to make sure there're
no problems in Device Manager before going on with the rest of the general Windows configuration, not knowing about that one little glitch which will bring the whole process to a screeching halt. So leave off installing the Rapid Storage Drivers until you
do your Windows Updates for the time being and hopefully Intel will fix this serious problem more sooner than later.
One last note, my Windows 7 Pro is 32-bit, so they're apparently just as prone to the problem as the 64-bit versions.
Thanks again to Sheldon Cooper for this quick fix!
P.S. There was also one other odd give-away that there was a problem; Windows Defender (in Control Panel) would not update either, independent of Windows Update.