Along with my continuing "Windows Explorer has crashed" problems with Windows 7 RTM (triggered by right-clicking most of the time), I discovered another bug in Windows 7 that I had with XP and could never fix. First, I'll explain the XP problem. I have an old 320 gig IDE drive that use to by my primary boot drive. I put it in an external USB enclosure and use it as a NAS device. In XP, I used the "classic" desktop. If I took my NAS drive and hooked it up and left it powered on and did a reboot, when my computer came back to the desktop.... the desktop properties would revert to the default scheme. If I disconnect the NAS drive and change the desktop back to classic and reboot, it will still go back to the default desktop when everything loads back up. Only fix after weeks of working on it was to reinstall WinXP. I could never get the classic desktop to load no matter what. Now, with Windows 7, I had my account configured with no password. When I turned my computer on and let it boot, it would go straight to the desktop. I wasn't using the login screen. Last night I made the mistake of having my NAS drive powered up and attached to my computer and when it was almost to the desktop, I was hit with the login screen. I had to click on my name and then the desktop loaded. I tried for about an hour to get it back to going straight to the desktop and no luck. A system restore did NOT fix the problem. (Nor did doing a system restore fix the desktop theme problem in XP.) Since I've seen this really freaking bizarre problem on two different operating systems now and different motherboards, I think it's an issue with my NAS drive but what? How? Would somebody care to try and explain this issue? I've put this drive in different enclosures and same problem. The ONE thing I can think of..... since I've had this drive in that enclosure I don't think I've ever trashed the partition. When I put it in there, I just formatted it as a single drive, never deleted the partition via Disk Management but I don't see how/why that would make a difference.
Oh well, to fix this issue again, I'll reinstall the MSDN copy that will hopefully get released today. Maybe I can also get rid of the stupid Windows Explorer random crashing thing too.