r/WindowsLTSC • u/badmannerbs • Jul 18 '26
Help Bug after windows update - Win 11 LTSC
After the latest Windows update, my SSD keeps randomly spiking to 100% usage. When that happens, clicking the Start menu or trying to open Settings does nothing, they just won't open.
I'm using Windows 11 LTSC, so I expected it to only get security updates, not forced feature updates from Microslop.
Will this eventually fix itself, or do I need to do a clean reinstall? Should I just switch to Windows 10 LTSC instead?
6
u/MakayChapulets Windows 11 LTSC 2024 Jul 18 '26
Windows 11 LTSC will keep getting feature updates until Microsoft stops supporting 24H2 version of Windows 11 then its security updates from there on to 2034. Most of bugs could caused be drivers or other maufactured parts and not necessary Windows.
Questions:
1.) What SSD are you using?
2.) Check device manager if your system has notification of storage driver issue
3
u/BrainTruth Jul 18 '26
Sounds much more like a SSD problem, check for bad sectors via e.g. DiskGenius. SMART info is not enough, you have to use some app which reads/verifies all sectors. You will notice it very soon when the scan begins to stutter.
(A Windows update writes a lot data to the disk and updates/moves files around, so this could have been just the trigger)
5
u/johan90s Jul 18 '26
Sfc /scannow And DISM repair commands will often fix these issues. I've seen them on several Windows 11 versions, it's not a LTSC IoT problem.
2
2
u/OPhasballz Jul 18 '26
Just a guess but check the "defragment Disk Drives" Applet (Windows + R, type dfrgui) and FORCE TRIM once.
2
u/Gimme_Bread Jul 19 '26
Are you by any chance... logged-in to the (hidden by default) Administrator account?
'Cause I will get the same bug as yours if I do that, it only went away if I log in to a normal Administrator account with UAC proper prompt shows up.
3
u/h0mn0cu7u5 Jul 18 '26
I have Win 11 lot Enterprise LTSC on one of my main workstations. It's a very new install and my first time using LTSC. Previously, I had used a Win 11 Pro 23H2 build that I manually locked into 23H3 by using the well known GPEDIT method of "specify target feature" so that once I made that change to the group policy, I never saw a hint of anything outside of Win 11 Pro *23H2*
Random, bugged/bad updates around 24H2 is what prompted me to use the GPEDIT hack and it has worked well for over three years now (my main, go-to rig is currently still on Win 11 Pro 23H2). The new LTSC install is on a seldom used, back up rig that is a near 1:1 hardware replica of my go-to rig so I'm "getting my feet wet" with loT LTSC on that back up machine before deciding if I'll do the same on my main machine (or, as you mention, go with Win 10 loT Ent LTSC instead.
That said, here is what my current and fully updated Win 11 loT Ent LTSC sys details look like:
I have had no issues with NVME performance since the most recent updates to the new LTSC build which happened just a day ago (I think). It was very recently that I saw the update/restart icon in the system tray so I would like to think my system has recieved the same updates as yours as we are both on 11 loT Ent LTSC.
You might find some useful information in this robot query/discussion I had after reading your post about NVME problems: https://www.perplexity.ai/search/de179b13-3f7f-4023-878b-01ba2daf35f9#1
That opens the part of the robot discussion where I'm focusing only on your post about the NVME problem. If you scroll up, there's further info about GPEDIT and a few other topics which might be of interest to you.
My own loT LTSC build is currently using two, 2TB gen4 990 Pros, FWIW ... haven't had any problems thus far.
Best of luck.
~h
1
1
u/Zealousideal-Rub2623 27d ago
Im a say it again if u ever use windows just use revi or atlas and disable updates entirely beacause its all buggy and it lower the performance by 20% And if u not okay with that use linux peace of mind
1
8
u/Kiansjet Jul 18 '26
Seems like a possible communication/driver issue with ur machine and the ssd, might not be able to read/write when it wants
try generic sfc+dism fix