That Sucked
So after all of the kvetching M$ has been doing about upgrading to Win10 and reading about all of the people who have upgraded with no problems, I decided to to go ahead and load it on the big box and ,,, it crashed and burned.
I should have known better. There is no way of telling why it generated the error code, actually the error code is fairly pointless as it doesn’t actually tell you what broke, only a list of what might be the problem, as in the utility that was supposed to check to be sure that the hardware was compatible with Win 10 may not have told the truth when it said “Of course it is!”
I’ll check later, because I have other things going on, but I won’t attempt to change this machine until I figure out what is going on.
13 comments
Sorry about your mess, Bryan. I did the upgrade a couple of weeks ago when my brother, the retired M$ executive, was here to hold my hand through the abyss. No problems except that it changed all my sound effects from the old single “ping” when an e-mail arrived to a multi-tone doorbell sound. It’s also way too “helpful,” kind of like the long-dead and not-mourned “Clippie.”
But you’re not the first person I’ve heard about that had a lot of problems. And you won’t be the last.
This is not a straight forward machine – it has an AMD vice an Intel processor and it dual boots Win7 and Linux on separate hard drives. I have two XP machines, the Raspberry Pi, the iPad, and this Toshiba laptop. The annoying part is that the big box isn’t required to do anything at the moment, so this was the best time to have it down.
Given my experience with Microsoft, I should have known better.
Geez, Bryan, so sorry that your experience upgrading didn’t pan out. But I feel for you as I’ve definitely been there myself. It was a nailbiter during the whole 10 upgrade process wondering if I was going to have another reformat ahead of me. So much fun that was, I can tell you. Not.
Good luck from the Blue Ridge!
There is no way of knowing what’s going on, and now we are in the regular monthly patch cycle and I have to patch the exiting system before I can do the update. What’s annoying is that they can’t point you in the direction of the problem, they basically say try a couple of dozen different things and we’ll see what works. It’s really annoying.
Eh, that’s one reason why I added a new SSD to my big desktop and installed Windows 10 on that rather than attempting an upgrade. Sometimes it’s wise to admit that just because you theoretically *can* do something, doesn’t mean you *should*. Heh.
In addition to every thing else, it dislikes my anti-virus program, ESET and even has generated a separate error code for the software that I have been using for almost a decade, and which there “checker” said was compatible with Win 10.
Oh, I have also seen reports that the replacement for IE [?Edge?] has a tendency to crash a lot on machines with AMD graphics cards.
This is the stable, more secure version of Windows, right?
Update: The error is 800703ED and it seems to translate as “I don’t like the grub loader.” I try a boot without grub tomorrow if the 17 or so Win7 updates that ESET says exists are actually discovered.
Edge is at this point a beta product. I don’t use it, I use Chrome or, for the few sites that require it, IE. In the future Edge will be production quality, but that future isn’t now.
Windows 10 definitely wants control of the boot sector. One thing about having a different drive for Windows is that I can give that to Windows, and just use F11 when I boot to choose which OS I want to boot into (F11 is my BIOS’s boot menu key). Not that I run Linux on my gaming system, that’s what the rack mount server is for!
Which reminds me, I measured my Antec case for the gaming computer and it’s just the right height to fit on the shelf in the rack. So my “desktop” computer is about to become a rack-mount computer, more or less. It simplifies the wiring considerably to have all the power and networking and KVM all right there in that one single cabinet.
Which reminds me that I scored an expander that I need to put on the shelf above, that will let me test SES with an expander more easily. I also want to re-arrange my server to put all the data onto the 6-disk RAID10 array, which is approximately 3x faster than the 2-disk RAID1 array that it’s currently sitting on. The question of what filesystem to use is an issue, BTRFS loses data too easily, ZFS really wants control of the drives, so I guess I’ll just put it on hoary old XFS and do the snapshotting and compression on the backup drive, sigh…
Badtux is right. The boot sector is one of the issues I had with win 10. Also, as with past Win versions, updating from a previous release rarely works without problems. A clean install is often the best. Another problem I had with win 10 was it tried to configure itself for UEFI disk mode by default rather than AHCI. Which I could understand if you are setting up a RAID which is what UEFI mode is for. UEFI also requires BIOS support, & in some cases (for new hardware like mine) Intel UEFI drivers during install, UEFI is only supported by win 8.1 & 10. There is a hack for Win 7, but I haven’t tried it yet.
Windows 10’s Secure Boot requirement could make installing Linux a big headache
Windows is loaded on its own separate disk and changing the boot disk is all I have to do to change that condition, but it would have been “professional” for them to have noticed that the machine was dual boot, like Linux did. It is more than slightly annoying that the free software pays more attention to users that the stuff that costs you big bucks. I’m on my third major version of Ubuntu and never lost anything. I had 1 blip, was told about it, was told what to do about , and everything worked after the minor fix and a re-start of the upgrade. Linux sees the Window drive, but Windows doesn’t know about the Linux drive.
“they basically say try a couple of dozen different things and we’ll see what works”
Exactly!!! In the early days, I would go to the Microsoft website to see what to do about an Error code, but I learned quickly that that was the way into the Twilight Zone. There would be reams of things you were supposed to “try”, and you could spend days wading through them all.
With all the money that Microsoft has made on us with arguably one of the most complicated computer systems in the world, why they cannot have a drill down type troubleshooting system is beyond me. You know, like: “Is your machine doing x or y?” or “When you do ___, does your machine do x or y?”.
These people are programmers after all! Either/or? If/when? Zeros or ones…
Rant over. This is what comes over me whenever anyone mentions Microsoft Error Code. 👿
But Juanita, those are expert programs designs for simple things like fixing cars or diagnosing illnesses, not complicated things like who gets blamed for the crummy programming that not only didn’t fix the original problem, but created two more … 😈
An Error code should have a meaning, even if the meaning is “Damn, we sure didn’t expect that to happen. You have insurance, right?” “Who knows?” is not a valid Error code.
Tech companies view QA and customer support as costs, not investments, and get what that mentality entails. What I found out at a previous company is that you can ship utter crap for twice what it’s worth if you’re willing to provide a level of handholding and support that customers have never experienced before. But Microsoft has always been bottom feeders unwilling to do that and they still have that bottom feeder mentality.
They don’t want to hire experienced people to deal with problems. The majority of the good answers I have seen about M$ products has come from other users who have taken the time to figure out what is going on and to report on it in fora.
I’m still working on the upgrade.