this post was submitted on 15 Oct 2026
438 points (97.8% liked)
PC Gaming
15671 readers
263 users here now
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Ran it regularly before and after the scheduled update every three months. Also ran a scheduled CHKDSK and DISM. Basically took a full day for routine updates. Cleared temporary files and unused AppData. Defragmented. I also frequently flushed DNS cache.
The fact that it's not an issue with any individual hardware should have tipped you off that it's not an "error" but just the way Windows is. You can find unresolved forums posts about this kind of issue going back to the early days of Windows 7 if you search.
If anybody is stupid enough to still use windows this is my advice: Enable the Hibernate option. It saves the RAM to disk and then resumes from there on startup, skipping any issues.
I actually suspect it started on the LTSC copy specifically after the Windows Store was installed, which cannot be undone.
I run Linux for everything at home...after W10 came out. But work issue machines are Windows. They have never had boot issues...they have a shit ton of other quirks though.