Well, I have another update, and, since I have a little more time, I can go into more detail:

First; The Microsoft tech support....I remember back when I first got into Unix based OSs, I was looking up some Linux / BSD / Unix Humor, and one of them was a web site that was basically a mix of quotes, and some jokes, about Windows, and I was reading it.

Well, one of the lines on that page was about Microsoft tech support, and how in most cases, if they don't have a really simple fix, they tell you to reinstall the OS.

I'd never had any experience with it personally, because the very first time I ever called tech support, was because my ISP was screwing up and I called them. The second time I ever called, was because a Windows Authentication wouldn't work in XP like two years ago, and today, my Wife called, and this was after I had to lookup the phone number and try multiple settings on their site to get a damn phone number.

The guy who answered finally, said it was customer service even though the site said it was tech support, and he gave a number for support, which turned out to be the stupid Windows Product Key line... So we were given ANOTHER phone number.

I don't know who this girl was, but she was NOT qualified to do that job.... My Wife was on the phone for an hour and a half, and at one point, she said "What directory are You in?" and my Wife told her, and she said to do "cd .." and then "cd Windows".... Which put my Wife in the directory She was in before....

The woman seemed to be on google trying to find a solution, because every time she said something, it was something I had tried a few hours earlier. Then she said to try the last thing I had tried before giving up, and I was like OMG....

The woman said she couldn't help, and she kept putting my Wife on hold to "Check for someone who might be able to help" and of course, she couldn't.

So basically she said that she couldn't help, and we would have to reinstall the OS.... From what I saw on Google, it was possible to fix this issue, but no one actually posted how.

I grabbed a Rescue CD, and booted from that. I did a check on the HD, and it said everything was OK, no bad sectors, nothing. From what I read on Google, and from what the girl on tech support said, the reason it happened, was that Windows Update corrupted a file.

I couldn't Believe it... She had managed to "find some commands" that would reveal some info about the Operating System, and what had happened, and basically, when Windows update grabbed the installation for a patch, it started to install, and while messing with some critical system files, it failed.

When it failed, it corrupted a file, and did this... I saw the message that it was a corrupted file and then girl on the phone said that it was a known issue. Since it was a "known issue" we "didn't have to pay for the call".... Couldn't Believe it.

According to the tests that were ran, the hardware itself is fine, but because of one update that auto downloaded itself and then crashed the machine, it started a mess.

I don't even remember which update it was, but basically, they said they knew about it, and that during the update process, Windows Update starts to change some important ****, and then screws up, fails, and the machine can't boot Windows anymore. And since the Windows Recovery Console can't find it, as it's basically one portion, it can't be fixed through that, so you have to reinstall.

The woman on the phone had us try Restore points again, which of course didn't work. I couldn't remember exactly which system files were corrupted, but Windows Update will basically fail as it's doing this, and winload.exe or something like that, gets corrupted. Like I said; I can't remember the exact name of it, but it's something similar to "Winload" or something like that, and it was corrupted during the update when it failed, and then, Windows can no longer load.

I can't Believe they couldn't find a way to get this thing from the Windows Disc.... I mean, I thought it would be copying a file, or a few of them, from the CD, and then rebooting, and it would be finished. But apparently you can't do that, which is REALLY stupid....

I'm exhausted. I've been up for a REALLY long time, and I didn't sleep very well yesterday either, so, basically, I barely slept, and then on top of that, I've been up for a really long time. So my thought process is really messed up right now, and it's hard to type this post in a legible manner.