If you read about closer paying attention to what is specific I think you will find it had nothing to do with the mouse at all but a glitch in the upgrade on the SSD itself.
"... logical block address....for Disk 3.... was tried" indicates the possibility that something is not quite on the 11099 build you have now getting in the way. Restarting after putting everything on hold in the msconfig tool's Startup tab for the minimum startup may see the upgrade go through when only the bare essentials are running to allow the complete unpack of the setup files needed during the download and initial stage before the automatic restart.Reset to device, \Device\RaidPort0, was issued.
The IO operation at logical block address 0x40233e0 for Disk 3 (PDO name: \Device\00000030) was retried.
Now at 13% on the second 10 Pro Insider Preview VM.
I would try something else. Did a restart to make sure all was good.
Bluescreen again and I cannot get past it. Can't get into safe mode or windows at all. Completely hosed the OS.
What a freaking update. I am at work for the next 10 days still and no usb with iso on it. Thanks a lot MS.
This whole sorry episode will conclude my time in fast ring and insider for sure.
My VMware 12 Player wouldn't work after this last update. Had to reinstall it.
Despite the update knocking a couple of minor items like one I won't be replacing anyways being a taskbar tweaker I had looked over once some four updates one for the Flash Player of all things as well as the MS Malicious Software Removal Program were all on the 14267 build went flying on as fast as it would take on VM however which tends to be a little slower or sometimes a bit faster then the physical upgrade by updates.
And there you go! The hidden system administrator came to life! Someone was asking how the right click to take ownership addition to the context menu would be on the system account compared to the average user admin. Well I'll have a chance now to give that one a good workout!