Win7 SP1 Update not installing - mismatched Mail file. 0x80004005

Good luck with the pool match!

The Event Viewer has held up through several reboots so we may have that one nailed.

"Well if it's not one thing, it's your mother."

Now I have another weirdness, it may be caused by the above, it may be coincidental. It seems something is setting a Read-only attribute throughout many of the files and folders in my system. I can uncheck it and let the change propogate through subordinate files and folders, but it returns a while later. I haven't found a pattern to it yet. It seems to interfere mostly with the AppData folder and config.msi when attempting to install software. Have you ever heard of something like this? Any ideas how to sniff it out? (And should I be starting a new thread on this?)

Doing that now - AFK while it runs - thanks.

My experience with SP1 is as follows, if it fails to update then you can do two options, re-installing windows 7 new build, or run the windows 7 original disc and run the upgrade option and re-activate windows 7, you might have to type the product key again. This comes straight from microsoft if SP1 fails to install, i spent hours trying to figure this out and did a lot of searching. Ultimately i choose the upgrade option to prevent from loosing any data or programs, hence it worked, good luck!

@rsedgarroman
Thanks for your suggestion. I am very aware that the first suggestion from M$ techs is to reinstall, but now that SP1 has successfully installed and we have invested 40+ hours getting here and are down to just a few small issues, I would rather persevere on solving the last issue. If a solution does not come, then I may end up taking the reinstall-upgrade path.

@Noel,
Sorry for the long delay - I had no idea a full scan would take 21 hours!
A couple things were found - e-mails in the Deleted Mail folder that I had deleted without opening but not yet purged due to suspicious senders.
A couple Java classes in the appdata java cache.
Both have been removed and I am testing to see if the read-only issue persists. I'll report back in the morning.

Best regards,
Duke

@Noel -

I discovered the final culprit. The Drobo backup software I use had gotten way far behind in syncing with the backup (disabled throughout this process) and was leaving file locks in place longer than usual as it struggled to append an ever-growing image synch table/queue. Once I disabled that service, the symptoms went away. Just need to reconnect the backup array and let the thing catch up with all the activity over the last week.

Looks like I'm back in business and I am incredibly grateful for all you have done to get me there! Hope I can pay it forward!