October 8th Microsoft released update Kb2862330:
This security update installs a newer version of usbport.sys file into the "\windows\system32\drivers
" folder, and forces a reboot. Every XP system on my network with XP that ran the update (about 100) went into a reboot loop. Safe mode, or any other options available at F8 would not get me to the drive. I had to pull all the drives hook them up to a system with a USB sled and copy the older version of the file back on to the system.
My guess is the new driver is stepping on memory of another file or vice versa. So, it would seem that I may have some old files and some new ones, as I read it may be due to the way my loads were created on my older Microsoft RIS server.
When we first started making loads on the RIS server we used an XP with SP2 OS disk. As time went on SP3 was released and we started loading it on our new installs. I had this same problem with SP3 rebooting the machines due to usbport.sys, but the fix I found on one of the Microsoft Forums was just to copy the older file back in. So I scripted my SP3 install to do just that and all was fine.
I read an article that only briefly touched on this particular scenario. If you are doing your base install from an XP SP2 disk but your load on the server have been upgraded to SP3, you can get a mixture of driver files.
Is this true?
If so, can I fix it?
Right now I have my critical and security updates disable on all XP systems (200+ across 5 locations.)
Thanks for any help