Rather odd 'failure to update' loop.

[Luna TGaP]

Recently I installed a new HDD and although it took a while, I eventually got it to work (it is replacing my old one, not working alongside it). The day after when it booted up, it got stuck in a typical 'failure to update' loop. I didn't have any backups or system restore points as the HDD was new and I was somewhat too keen in destroying my old one, so I went into safe mode, uninstalled the updates and disabled updating (a couple of days of trying to get this to work without any of that were involved, but there was just a lot of not working so I'll leave it out) and that solved my problem, until today. I got stuck in the same loop as before today, however when I went into safe mode, it said no updates or even programs had been installed since 02/09/14. This was excluding the drivers for my new Perixx MX-2000II mouse, but I uninstalled the drivers and unplugged the mouse before rebooting normally. The odd part was when I rebooted I was still getting the failure to update loop, despite no updates being present. One more thing to note is the drivers package and the mouse itself work fine in safe mode. Thanks in advance for your help I'll get a hold of the logs in the 'Windows Update Posting Instructions' as soon as my computer will let me. :S

 

[Luna TGaP]

Nevermind. Although the problem still stands, I have a restore point for 02/09/14 so I'll use that. Not sure how to delete the thread but if anyone with the power to finds this, go for it. I won't mark it as solved as it wouldn't surprise me, but once I'm logged on I'll create another restore point just in case so I should still be able to access my computer for those logs or whatever it is that you need.

 

[NoelDP]

Please follow the Windows Update Posting Instructions and post the requested data
If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)