Dont use Windows 10 LTSC ver. 1903 with Classic WoW!

WoW Classic WoW Classic General Discussion
1

Just wanted to inform fellow players that this version is fundamentally broken and if you want to save yourself some headaches then either use regular Windows 10 or LTSC ver. 1809.

The bug that has been appearing for a lot of us (seemingly at random) is that a random process gets its CPU usage boosted up to 100% (can be WoW, Nvidia, Firefox, Windows, anything really) and crashes/freezes your PC. I even tried on a completely fresh install to block updates and only install Classic WoW and tried playing it and this bug STILL happens so it’s guaranteed not to be some random software, and done tons of hardware tests and tried pretty much every fix that comes up in google, updating bios etc so it’s certain to be a Windows issue by now.

I’m gonna revert to ver. 1809 tomorrow and see if that fixes the CPU usage bug, but for all you people experiencing similar issues or are planning on upgrading to LTSC to get rid off W10 bloat, don’t get version 1903 of it. Don’t be like me and waste upwards to 20 hours trying to fix a fundamentally broken OS, use that time to grind pre-bis instead!

1 Like
2

Not had this happen ever, and I’ve been on 1903 for quite a while. Then again I do have 6 cores.

1 Like
3

I thought even a potato had at least 6 cores these days.

1 Like
4

Hmm, I have also had no issues with 1903 nor the next update 1909, however, my computer is fairly powerful so that could have covered it up.

1 Like
5

It isn’t possible to block windows 10 from talking to MS - it’s a service not an OS

You can disable the windows update service but the machine will still talk to MS

I use MAC OS - it’s much more stable and uses far less hardware resource to be up and stable

6

Now now - 6 core processors are still bleeding edge within the home - that is not off the shelf home PC at this stage

7

Can you count on more than two hands how much software is compatible with your OS yet?

1 Like
8

Mac Mojave is exceptionally good - it’s runs everything I want it to

I have to say that I have never had an issue running WoW on Mac these past 6 years since I made the change - the same cannot be said of Windows

9

But can it run Crysis?

10

Could attempt 1909 and see if that fixes the bug, have Microsoft released an ISO for it yet or is it still only early access?

11

Don’t even know what that is - which is what I stated - it runs everything I need it to

You can run parallels desktop though - so I imagine it wouldn’t be an issue

I did finally set up the eGPU - it’s incredible hardware - and stable

12

I’m on the Release Preview, so should be available in the next week or so

1 Like
13

Been running 1903 on a potato PC had no issues with CPU usage / Disk IO issues. Classic / BfA both behave themselves, and run without any issues at all.

Have you run any hardware diagnostics or the upgrade compatibility wizard to see if there are any underlying problems?

14

Been running 1903 on a potato PC had no issues with CPU usage / Disk IO issues. Classic / BfA both behave themselves, and run without any issues at all.

Have you run any hardware diagnostics or the upgrade compatibility wizard to see if there are any underlying problems?

I’ve ran half a dozen of tests, re-seated my CPU twice, upgraded BIOS, both changed/removed overclock settings etc etc. As said I’ve spent roughly 15h trying to fix this so I’m very certain that Windows is the problem by now.

Tried pretty much every solution offered in Google without any of it working and it seems Windows have credited the bug being a thing which they don’t tend to do unless it affects a lot of users. Kinda like how part of the Mac advertising back in the day was that they couldn’t get any viruses (which was a blatant lie) so if anyone had gotten a virus and called their customer support for help then they had been instructed not to tell them they’d got a virus. PR, scummy large companies and all that kinda jazz. Anyway according to Windows they have already released a patch for the issue which fixes it (though according to some users it breaks it even more) yet it doesn’t even show up in Windows update and when you try to install in manually (download and run the patch file) Windows will just give you an error message. Kinda leads me to believe that it was true that the patch broke the OS (more) so they took action to stop people from installing it, all while having provided a ‘‘solution’’ for their earlier bug. Wish Bill Gates would save some of the money going to the third world for hiring competent devs for his company…

I’m on the Release Preview, so should be available in the next week or so

Figured that would be the case but it doesn’t hurt asking! From what I heard 1909 was supposed to go public in the end of September (though it wouldn’t be strange if it got pushed back a week or so due to fixes) so it should be accessible fairly soon. Guess I’ll make do with what I have until then, since from what I’ve read, earlier LTSC versions can get the bug as well.

15

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.