Everything seems to match up alright, This might be a dumb question but there seems to be a small file size difference does this matter at all?
This seems to have worked, I tried to install the 83GB one anyway like you said and it failed but then when I searched again it was not found anymore.
Correct me if I'm wrong but isn't Enterprise up to 2004 update not 1809? I had a look at the iso download and noticed there all 1809. I haven't been keeping up to date with all this new fangled upgrading and updating stuff but I thought seeing I'm going Zen 3 in a few weeks I should move from the 2016 LTSB version I'm currently running. Thought it'd be as easy as grabbing the latest iso and installing like I normally do but after looking around is that not how it works now?
Enterprise and server 2019 LTSC are of the 1809 (17763.xxxx) family. It's not really working correctly with zen cpus, afaik, that's fixed in 1903 and up. LTSB > LTSC can be done by ISO. LTSB/C > normal Enterprise too.
Ok so with these older 1809 iso's do we have to inject the updates or can we actually get more up to date iso's for Enterprise? Sorry I'm use to just getting the latest untouched iso, installing it, cracking and done. I've looked around and cant find anything aside from the eval iso's which are useless to me.
All available and officially released Enterprise 2019 LTSC ISOs and info can be found here, the latest is 17763.316:
Switched from LTSB to LTSC recently, fresh install using KMSPico to activate (as I had done for last couple of years on LTSB) I'm curious if MS has such protection to shutdown the machine if it sees it as non-genuine? Maybe the software protection service? The pc has been shutting down for the last two days just randomly, in the event logs I see the shutdown requests and all of them are apparently issued by the user - which isn't me pressing a button. I know it is not thermals, checked the various monitors, but I am also thinking maybe psu is finally giving out after a fair few years (10+) because on some occasions the pc will try and restart despite the bios settings being such that in power events it just stays off. Maybe psu is surging or something which causes the system to try and start on its own, all I see for the voltages is the cache voltage not registering correctly sometimes.
If you know how to bridge the psu(run it completely unplugged from the motherboard/components), grab a multimeter and start poking at the 12, 5 and 3.3 volt rails. If you see voltages that are drastically different than what the rail should be sustaining, you have your answer. To my knowledge, no, windows doesn't shut itself down just because it knows it's not genuine or you've used 3rd party soft to activate.
Yeah, know how-to but no multimeter :/ But if Windows doesn't do this then tends to point the finger to the psu, as said it is old and has served well but looks like may have finally given up. Ta muchly
Cheers, did similar with Aida64 just to see what was what. I think it is the psu due to the behaviour and the issues seen with the cache voltage so I'll grab a new one and see how it goes. I have couple of laptops with same ltsc build and they are fine, so more pointing to the psu being on the last legs.
This is a bad unreliable way of "testing" your PSU. Any old and or bad PSU is usually able to get good voltages on the rails in that situation. What is far more important and the actual reason for instability is the question if the PSU can maintain good voltages when the voltage rails are under load. Bridging the PSU means zero load and so those measurements don't really mean anything.