Overclock.net banner
1 - 20 of 74 Posts

@purple

· Registered
Joined
·
92 Posts
Discussion starter · #1 ·
I tried to upgrade to 11 about 3 times now, but every time without luck. Every time it got stuck at 60%, and then it restarts. I added some pictures with my phone. (sorry for the bad quality)

If someone had a similar issue, please let me know.
 

Attachments

A list of hardware and bios version (motherboard) would help. Generally this issue is from a bad ISO file or incompatible hardware/driver.
 
Discussion starter · #3 · (Edited)
Motherboard: Rog Strix X570 Gaming - E (bios 4002)
CPU: Ryzen 5900x
RAM: G skill 3600 32GB
PSU: Rog Thor 850W
GPU: Strix 2080
NVME: Sabrent 1TB
SSD: WD 250GB
Mouse, keyboard, and a headset from Logitech

Windows was downloaded from the update (windows insider program)
There could be an issue from one of drivers but not sure which one.
I disabled all startup programs but it didn't help.
 
TheBDK is correct. Lots of folks are going to be disappointed when the W11 hardware requirements finally sink in. For me it's having to deal with the "Secure" mode.
 
This is why I didn't want to be first on my block for W11. If you Google the bug you'll see that it's part of a developmental thing as the programmers are having to deal with it. Could be incompatible HDs as well as cabling, etc. I see no benefit in jumping the gun on this. Even if you're a Windows Insider it's going to be a tough road until the final release. Save yourself some grief and go back if you can.
 
  • Rep+
Reactions: @purple
I just did the update from the Beta Channel. It acted more like a major feature update. Rebooted a couple of times and I still have the option to roll right back to 10. All apps and drivers remained in place and work fine. I did the alpha on an unused rig and after several reinstalls and drivers not working I just stay in the beta channel. They just rolled out another update a few days ago.
 
Just to confirm OP tried these options?
Also a couple of things:
1. For the love of God, clean the lens of whatever camera you took those shots with.
2. Windows 11 is in beta and Microsoft has been opaque at best about the TPM requirements so, if you tried these two things and you are on a legit upgrade channel, I’d say just wait until an update to the beta occurs or try a fresh install on a new drive.
 
The Beta channel is on its second version. Just update mine yesterday. I hang back in Beta channel as I’ve had enough of doing reinstalls on alphas over the years. If you have a legit and activated copy of win10 and a M$ account as well as TPM it’s easy. I just had beta channel down on the insider program and it was more like a feature update both times and I can still roll back to 10 at the click of a button. A lot of the issues are folks running the leaked version that was very raw alpha and half the sources have taken time to embed malware all because they weren’t running legit with an activated license and M$ account.
 
Discussion starter · #15 · (Edited)
JustinThyme

Everything was updated and enabled for W11, also used that command a couple of times without any error. I've been searching for a solution this whole week but didn't have any luck. I am positive that clean installation of windows would do the trick, but I got too many important files to go with this route.
 
Have you tried using disk cleanup and ditching the delivery optimization files? Might be that something is corrupt in the first part of the download. Also unplug all unnecessary devices.
Does it just hang there then do a reboot telling you to pI$$ up a rope or does it hang there and you are doing a hard shut down. Seems to me I recall there being a stall at 60% while mine was installing which is more or less normal. I just got up and walked away and left it and checked every few minutes and eventually I was at a log in screen. I wouldn’t trust a clean install it the update method that gives you a choice to go back fails. I didn’t download anything. I just had insider program and beta channel enabled and it came like a feature update through Windows update. No ISO, no media on USB just watching it say downloading in Windows update then installing followed by your device needs to be restarted to complete update, clicked restart and got the usual screens. Except they changed the wording now. It’s slipping my mind ATM exactly what it says but it’s not the same, just slightly different. Dev channel has ISOs to do a clean install and I’m not sure how that would go over trying to update your current OS with an ISO for clean install.
Have to reached out to M$? There’s a support feature in win10 where you can open a chat window if you have a valid retail license or take the slow boat and use the feedback hub for the insider program and list your machine specs, what’s installed etc. could be either a driver thing or a program that’s not compatible. All I can say it my HEDT updated flawlessly once it hit beta. I tried the alpha on the Dev channel on an idle machine as a clean install when they first released it and had issues booting in the first place then right out of the gate network drivers wouldn’t install and what was being forced by the OS didn’t work either so had to use the 1Gb connection instead of 10Gbe. It dumped multiple times just trying to install software and a few reinstalls later I said screw this and parked my a$$ in the beta channel. I’d been doing early testing for a long time but don’t have the patience for it anymore. Worst one ever was code name Longhorn that you had to have an MSDN subscription to get and what a POS from inception to completion aka Vista. Didn’t work for sheet in the beginning then all drivers and software had to be installed and run in compatibility mode for win 98.
 
Discussion starter · #17 ·
"TLTR," mate. No disrespect to you, my man.

I know you want to help, but I'm too tired to even start with it. I have found something about my problem, and Microsoft is working on it.

"We’re working on a fix for a second issue causing some devices to fail when updating to this build with error code 0xc1900101. When the update fails, it will roll back to the previous build. If you are encountering this issue, we recommend pausing updates until we release a build with the fix."

I keep receiving this error after failed update.
 
"TLTR," mate. No disrespect to you, my man.

I know you want to help, but I'm too tired to even start with it. I have found something about my problem, and Microsoft is working on it.

"We’re working on a fix for a second issue causing some devices to fail when updating to this build with error code 0xc1900101. When the update fails, it will roll back to the previous build. If you are encountering this issue, we recommend pausing updates until we release a build with the fix."

I keep receiving this error after failed update.
Great that you reported the error. Feedback is what makes the RTC less troublesome and the reason they introduced the insider program. While they do a lot of in-house testing they can’t possibly replicate every machine with all its devices. The only issue I had that didn’t cause it to not install but prevented my 10GBe Ethernet from working was reported and actually fixed quickly, less than a week.
 
This was happening to me.Turns out that I had a disk in my DVD drive.I removed the disk and all was well.
Mario Andretti with a DVD drive? LOL
I have an external ASUS USB C DVD drive that mostly just gives me something else to dust. Ive turned it on like twice since I bought it several years ago. I have GTAV on DVD takes like 10 hours to load via disk and 15 mins tops via website. Optical drives are just too slow now. I did use it a lot when I first got it ripping my Bluray collection and a few DVD movies and reencoding them and putting them on my NAS so I can use Plex to view from anywhere with anything that can get an internet connection. Even adjust and reencodes for resolution on the fly as 4K on a mobile phone is far more than needed.

Thats a boot setting for it to look for DVD. Im surprised that it went with CSM enabled.
 
1 - 20 of 74 Posts