Upgrading From Windows 1.0 to Windows 8 On Actual Hardware

You are the person I'm talking about when I say that people that blame Windows for problems are their own worst enemy, and it's way worse when Dunning-Kruger is in full effect as well... > Inexperience with a computer doesn't cause ntdll to break. Inexperience with a computer doesn't cause Windows activation to break. Inexperience with a computer doesn't cause shutdowns to take hours instead of seconds. Inexperience with a computer doesn't cause suspend to spontaneously bork. Inexperience causes all these things. Listen, my experience goes way, way beyond 'anecdotal' when it comes to managing end users running Windows. Never, ever, ever with the exception of a small handful of updates, does Windows fundamentally break itself. When you see a bluescreen, 100% of the time it is your fault or it's your hardware's fault. 100% of the time. Sometimes it might look like it's not your fault. Sometimes it's McAfee removing important files that break the OS because it's being stupid, but that's not a Window's problem. If shutdowns are taking awhile, something is broken. Your inability to diagnose that isn't the fault of the OS. Ever. If your computer 'suddenly borks', then your hardware failed, or you are bad at computer. 100% of the time. If you can't manage to upgrade Windows, than I can't help you. Someone did it from 1.0 to 6.2 in a straight shot: [this video] When stuff like this happens: > According to jjoonathan, the ntdll segfaults started happening after an update It usually means t