Problems with Windows 10 on outdated systems
Problems with Windows 10 on outdated systems
Because my alarm didn’t go off yesterday, I slept in and missed my maths test. Luckily, my teacher was quite understanding, so he let me take the exam in his office during the afternoon, together with another student studying remotely (I’m not sure if that’s the term used in English, but whatever it is). Some of the questions were answered on a PC. Since he only had one there, he borrowed his laptop from me. As expected, Windows 10 began updating itself at an inconvenient time. Naturally, he started complaining about how Windows 10 is terrible, and how Windows 7 was so much better (which I agree with). This brought back memories of the problems I faced with it before.
Before setting up my Ryzen system, I’d used Windows 10 on an older machine a few times during free update windows. That PC had an Athlon 64 x2 6000+, GeForce 8500 GT, a generic Gigabyte board, a few old SATA HDDs (128, 256, and 480 GB), split into at least two partitions because I’d taken them from dead computers, and I didn’t bother formatting them. There were also six GB of RAM, with all modules being different. I experienced various oddities with the operating system. The most frequent issue was that updates wouldn’t install properly. Every time I powered it on, it would try to set up the updates, get stuck midway, and restart after a few minutes. This cycle repeated roughly three times before it gave up and claimed the update failed, requiring a rollback.
I then returned to Windows 7 and attempted another Windows 10 installation later. This time, along with the previous problem, audio would cease working once the PC entered sleep mode, forcing me to reconnect the speakers each time. Another challenge arose when I tried it a third time (and again with the earlier issues). Programs that previously functioned stopped suddenly. I needed to finish some schoolwork in the evening, so I opened ArchiCAD. Instead of notifying me it was an educational version, it displayed an error saying the program wasn’t meant for Windows. Within days, most of my software started behaving this way, so I switched back to Windows 7.
After replacing the GeForce 8500 GT with an RX 470, I decided to try Windows 10 once more. The first problem happened right after installation. After a few days, parts of the OS stopped working entirely. I couldn’t access settings, open the power menu, or even use Edge—except for Chrome. Eventually, I gave up and returned to Windows 7.
Later, when updating to Ryzen, I was compelled to switch back to Windows 10 because Windows 7 didn’t support the AM4 platform, and several USB ports failed during installation. (I heard it might work with an old PS/2 mouse, but my Strix B350-F doesn’t have one.) By the end, only the 480 GB HDD remained from my old machine, which I still used as a primary boot drive, but it continued to cause problems during updates. This issue ended when I swapped that HDD out, after which everything started functioning correctly.
Does Windows 10 seem to dislike older hardware? Have you encountered similar problems?
Windows 10 has been a real pain in my professional life as an IT admin managing more than 1000 systems. We've faced far more problems with this OS than with anything I've ever handled before, even including Win98. We rely on the LTSB version, which is meant to be lighter, but honestly, it's so terrible I'm avoiding MS altogether now.
Just wondering if you've attempted to read your message? Adding a paragraph break here or there would really clarify things and improve the flow.
Windows 10 may require an update install if updates are blocked. You can choose Active Hours and enable a Windows 7-like restart window. Perhaps instead of wasting time, you can explore the available options. There could be several reasons updates fail—log files might help. Even though I installed Windows 10 on an older system, very old HDDs might be failing, or driver issues could be the cause, which is difficult to resolve without support. It seems like a problem with the OS version detection in ArchiCAD. Regardless, the solution is likely to run the program in compatibility mode, which probably would have resolved it. Since you mentioned the panels/program are all GPU-drawn, it might point to a GPU driver issue.
This term refers to the Long-term Servicing Branch in Microsoft's deployment processes. It describes a structured approach for managing updates and support over time. For more details, you can check the official documentation here: https://docs.microsoft.com/en-us/windows...s-overview
LTSB is intended for kiosks and POS systems, giving us greater influence over aspects like update timing, removing features such as Store and Candy Crush, and addressing issues like patch 1809. However, problems like patch 1809 underscore the challenges of working with Windows 10. Explaining the network chatter Win10 creates is a major concern—it strains our connections. Many users have faced the mapped drive disconnect bug, and we’ve encountered profile corruption that didn’t exist on older Windows versions. Network transfer issues are frequent (not because files are in use), making troubleshooting difficult. We’re forced to postpone patches for months while testing new updates on a small group of systems to assess stability.
This applies to any high-priority issue where minimizing downtime is essential. Identify the root cause and adjust Windows settings. The upgrade stage was likely forced due to problems; details are available in public support resources. Bookmark this page for future updates. We encountered similar issues in Win7, which were resolved easily—though sometimes Norton was involved. There’s no mystery behind it. Follow your system’s settings carefully. Consider joining the Insider program for early insights.
The upgrade came unexpectedly. I'm employed by a government organization... Much of my work remains restricted (NDA requirements). I really wish I could leave the windows open, but that's not possible. A lot of my tasks are linked to tools like IE, which limits flexibility. This issue is something we'll discuss later, and it doesn't apply to this situation.
So then you're not on the LTSB or someone messed with the settings. With an 1809 update you're on the current branch, the same as consumers. Technical support will be your main concern. If you believe the situation is better elsewhere, check out some real-world examples. In short, governments and businesses that made the change went back to Windows. Financially speaking... I can rely on my workplace resources. We invest more in Linux support than if everything switched to Windows. But we can't. Windows Server doesn't give us the flexibility we need for our operations. All I can say is, before jumping to conclusions, it might be that something isn't set up correctly. Microsoft has a huge amount of documentation, but sometimes it's too much and people struggle to find what they need, especially when information is split between official docs and MS blog posts.