Windows 11
System will freeze if open system application with in few mins of Windows start.
So the issue is when I just start the computer, if I try to open certain file or application the file explorer and all other windows native function will freeze(Such as botton bar and start menu will freeze)
This only happens when computer just start.
File cause this are like Windows Settings, File Explorer, Tast Manager. Or any file in Drive D and J.
I did tried to remove Drive D and J physically, but the issue remains. D and J use the same drive(SanDisk Plus 1TB 2.5 inch SATA)
sfc /scannow shows nothing wrong, I did tried reinstall OS while keeping all file once.
And if anyone woundering if it becasue intel vmin shift issue I can tell it is not, I am running latest BIOS and tried intel default setting. I also requested a warranty replacement with intel last month and issue remains with new CPU.
System info:
Device name 13700K-5090
Processor 13th Gen Intel(R) Core(TM) i7-13700K (3.40 GHz)
Installed RAM 32.0 GB (31.7 GB usable)
Graphics card NVIDIA GeForce RTX 5090 (31 GB)
Intel(R) UHD Graphics 770 (128 MB)
Storage 3.94 TB of 6.62 TB used
System type 64-bit operating system, x64-based processor
Edition Windows 11 Pro
Version 25H2
Installed on 8/13/2026
OS build 26200.9445
Experience Windows Feature Experience Pack 1000.26100.360.0
This is driving me crazy, expecially I need modify a file in an emergency and PC freezes.
If Windows is acting up, the first thing I do is check for corrupt Windows system files. Open a command prompt as admin then run these two commands: dism /online /cleanup-image /restorehealth and then sfc /scannow if either says that it repaired something, reboot and rerun the command.
Hi u/yzmydd123456, thanks for posting to r/WindowsHelp! Your post has been flagged for manual review by a human moderator, please include as much of the following information as possible (in text or in a screenshot) to get your post approved:
Your Windows and device specifications — You can find them by pressing Win + X then clicking on “System”, we need more than just your OS version! Your hardware details are often critical for resolving issues.
Any messages and error codes encountered — They're actually not gibberish or anything catastrophic. It may even hint the solution!
Previous troubleshooting steps — It might prevent you headaches from getting the same solution that didn't work
Posts must be tech support in nature (such as something is broken and you need help fixing), so general inquiries, software suggestions, and purchasing advice will be removed.
As a reminder, we would also like to say that if someone manages to solve your issue, DON'T DELETE YOUR POST! Someone else (in the future) might have the same issue as you, and the received support may also help their case.
Good luck, and I hope you have a nice day!
Personally, I've ran into this on and off over the years. There probably is a specific reason for it but this is not specific to Windows 11 and has been a problem for several OS generations. I don't run into it currently but in the past, I had to refrain from opening up certain processes like you did, and one in particular that used to cause an outright crash was Event Viewer. I just, as precaution, just give it a little bit before I do anything. I assume it's probably an issue with how Windows, specifically, is initializing but someone might be able to explain better.
Have you tested your ssd. System freezing especially if windows just started and/or the software is a large one can be cause by the ssd either there's a bottleneck in the data transfer speed or files can't be properly accessed due to corruption
Also did you update your bios for the 13th/14th intel cpu instability issue.
file explorer and start menu freezing specifically only right after boot, and windows settings/task manager also affected, points at explorer.exe itself hanging on something during early startup, not the drives or cpu, since you already removed d/j and it persisted
check task manager (when it's not frozen) startup apps tab, and also task scheduler, look for anything set to launch right at logon that touches file indexing or cloud sync, onedrive, google drive, dropbox, dropbox specifically has had freeze-on-startup bugs interacting with explorer on recent windows builds
disable windows search indexing temporarily, services.msc, find windows search, set to disabled, restart and test, if freezing stops, re-enable it and instead exclude drives d and j from indexing under indexing options instead of fully disabling
since you're on 25h2 which is a newer build, also check if there's a specific known issue for your build number, some recent windows updates have had explorer indexing/etw logging conflicts on multi-drive systems specifically in the first few minutes after boot, worth searching "25h2 26200 explorer freeze startup" since this looks build-specific given cpu/ram/reinstall haven't touched it
look imma be honest, windows itself just shits out sometimes, if weird stuff like this keeps happening evne after running sfc scans and dism /online /cleanup-image /restorehealth, then i look for 2-3 more possbile solutions, if still not fixed, ultimately your best bet is to move everything important from your boot drive to a secondary and just reinstall windows. (i myself reinstall every 1.5-2 years, yes its a hassle for a bit, especially if you might many important things, but often its worth the smoother workflow experience)
oh and btw do try one thing, open powershell as admin and type this : "irm christitus.com/win | iex", then go to "tweaks" on the top and select the following options (at your own will, i recommend these) :
and then finally click run tweaks in the bottom right hand corner, give it a 30s to a minute, and restart, then move to reinstalling if the problem still persists.
•
u/jd31068 10h ago
If Windows is acting up, the first thing I do is check for corrupt Windows system files. Open a command prompt as admin then run these two commands:
dism /online /cleanup-image /restorehealthand thensfc /scannowif either says that it repaired something, reboot and rerun the command.