Because the response time on this message exceeded 2 business days, I
contacted concierge and then customer support, because I was unsure whether
the normally responsive msdn engineers were aware of this message. About 4
days after that, with no further response, I dealt with this corruption
problem through brute force. Although it took another day of my work to
reinstall SBS 2008, I have removed the problem.
Similarly, there would be no need to give further attention to this
newsgroup post.
Unless of course, you see value in describe the problem, and the
vulnerability in the update mechanism which I unwittingly triggered.
"jr (AT) nospam (DOT) nospam" <jeffleese (AT) hotmail (DOT) com> wrote
Quote:
Later in the day, I found the server was updating itself again, and this
time it resulted in a worse outcome. I got error 0x800f0826 and windows
update announced that the update was unsuccessful and was reverting.
It seems to have messed itself up quite badly. Is there someway to clear
up this corrupted update situation? |