• Happy holidays, folks! Thanks to each and every one of you for being part of the Tom's Hardware community!

Question Win10 stuck on Welcome screen

LikeABossNT

Distinguished
Mar 22, 2014
136
0
18,710
Hi,

My desktop has been functioning normally until today, no updates. haven't downloaded anything etc.
Earlier today I tried to shut down my pc, but it wouldn't completely turn off. Screen was black but the lights on my fans were still on for some reason.
Didn't think much about that and went grocery shopping.
Now that I've tried to turn on my pc again, I enter my password and it gets stuck on the windows welcome screen.

I've tried rebooting into safe mode, but it gets stuck there also.
I updated my BIOS and put that to default settings (they were mostly default anyways before, no OC) with no luck either.
Tried removing CMOS battery and holding down power button for 30s to reset it.
I've also tried disconnecting all devices, with only a monitor connected to the pc.

Now here's the weirdest part. I have another user profile on my PC with admin also, but that one doesn't have a password.
That profile gets past the welcome screen, but it's just a black screen. I can enter task manager, which works as normal, but nothing else works.
So it's just a black screen with task manager.

I feel like my windows somehow got corrupted, but I have no idea what I should do.
Nothing works in Troubleshoot mode, Safe mode or anything.
Anything else I can try?

EDIT:
Removed unnecessary hard drives also.

Specs:
CPU: Intel i7-13700k
MOBO: Gigabyte Z790 GAMING X AX
RAM: Kingston 32GB (2 x 16GB) Fury Beast DDR5, 5600MHz, CL36, 1,25V
GPU: Nvidia RTX 4070Ti SUPER
SSD: Kingston 1TB FURY Renegade PCIe 4.0 NVMe M.2 SSD
PSU: DeepCool 1000W PQ1000M
 
Last edited:
Solution
Not unless they both have exactly the same identical hardware installed including same CPU, motherboard, etc. Just having different chipset drivers because of different motherboards is enough to skew any results you might have and could possibly create other complications such as deactivating your installation. While that's unlikely, it's possible. But if you're willing to deal with the potential for creating a new issue, it might at least tell you if the problem is your current installation. Better might be to simply take a spare drive if you have one, remove your current drives (All of them), install the spare drive and do a clean install of Windows on THAT to see if it works normally. If so, then you pretty much know it's your...
Assuming you have all your important files from your Windows installation backed up elsewhere, and if you don't, well then this is going to be a lesson for you, I'd say a clean install is your most likely solution. Assuming it's not a hardware issue of course. Yes, there MAY be other options that could help restore your OS installation but the reality is that IF there is, it's likely going to take a lot more work and effort to get there and there are no guarantees that it's going to be effective. A clean install will immediately resolve the question as to whether the issue is a problem with Windows or a hardware issue.

It would also be very helpful to know what hardware we are dealing with and how old it is, because this also sounds like it COULD be something else such as a storage device corruption or sector problem, motherboard issue, etc. But I think Windows is the more probable culprit.

CPU, motherboard, memory kit, storage devices, power supply (Exact model please), etc. and some at least rough idea of exactly how old each of these components is.


In case you should ever need to do a CLEAN install of Windows, this guide will help to ensure it gets done properly.

How to do a CLEAN installation of Windows 10, the RIGHT way
 
Assuming you have all your important files from your Windows installation backed up elsewhere, and if you don't, well then this is going to be a lesson for you, I'd say a clean install is your most likely solution. Assuming it's not a hardware issue of course. Yes, there MAY be other options that could help restore your OS installation but the reality is that IF there is, it's likely going to take a lot more work and effort to get there and there are no guarantees that it's going to be effective. A clean install will immediately resolve the question as to whether the issue is a problem with Windows or a hardware issue.

It would also be very helpful to know what hardware we are dealing with and how old it is, because this also sounds like it COULD be something else such as a storage device corruption or sector problem, motherboard issue, etc. But I think Windows is the more probable culprit.

CPU, motherboard, memory kit, storage devices, power supply (Exact model please), etc. and some at least rough idea of exactly how old each of these components is.


In case you should ever need to do a CLEAN install of Windows, this guide will help to ensure it gets done properly.

How to do a CLEAN installation of Windows 10, the RIGHT way

I don't have everything backed up, so wanted to avoid clean install, but yea that would be the best solution.
The pc is about 2 years old, here are the specs:

CPU: Intel i7-13700k
MOBO: Gigabyte Z790 GAMING X AX
RAM: Kingston 32GB (2 x 16GB) Fury Beast DDR5, 5600MHz, CL36, 1,25V
GPU: Nvidia RTX 4070Ti SUPER
SSD: Kingston 1TB FURY Renegade PCIe 4.0 NVMe M.2 SSD
PSU: DeepCool 1000W PQ1000M

It also had a HDD connected, but while troubleshooting I removed it just in case, didn't help.
 
I've never seen much success on any system I attempted it on using the built in Windows utility, but given that you have no access now and will likely end up needing to do a clean install anyhow it's probably worth at least attempting to do a Windows startup repair if you haven't already.

https://www.tenforums.com/tutorials/27649-run-startup-repair-windows-10-a.html
I tried that earlier and it just said something like "couldn't diagnose your pc"
Do you think it would be a good idea to take out my main computers ssd and replace it with one from my old computer. Both have W10, just wondering if I can boot through that as a test, without messing up the licenses or files.
 
Not unless they both have exactly the same identical hardware installed including same CPU, motherboard, etc. Just having different chipset drivers because of different motherboards is enough to skew any results you might have and could possibly create other complications such as deactivating your installation. While that's unlikely, it's possible. But if you're willing to deal with the potential for creating a new issue, it might at least tell you if the problem is your current installation. Better might be to simply take a spare drive if you have one, remove your current drives (All of them), install the spare drive and do a clean install of Windows on THAT to see if it works normally. If so, then you pretty much know it's your Windows installation. If not, then it's likely something else.

Might even be worth simply buying a cheap drive to do this. You can get a 120gb Patriot burst elite, which isn't bad, I've used them in many cheap builds, for like 12 bucks on Amazon.
 
Solution
Not unless they both have exactly the same identical hardware installed including same CPU, motherboard, etc. Just having different chipset drivers because of different motherboards is enough to skew any results you might have and could possibly create other complications such as deactivating your installation. While that's unlikely, it's possible. But if you're willing to deal with the potential for creating a new issue, it might at least tell you if the problem is your current installation. Better might be to simply take a spare drive if you have one, remove your current drives (All of them), install the spare drive and do a clean install of Windows on THAT to see if it works normally. If so, then you pretty much know it's your Windows installation. If not, then it's likely something else.

Might even be worth simply buying a cheap drive to do this. You can get a 120gb Patriot burst elite, which isn't bad, I've used them in many cheap builds, for like 12 bucks on Amazon.
Ok that was going to be my next question haha
Thank you for the help, I'll try installing windows on an old spare hdd.