[DISCUSSION] Windows 10 1903/9 'FINAL' Build 18362/3.xxx (PC) [19H1/2 Release]

You need to login to view this posts content.

 

You need to login to view this posts content.

 

@MrMagic:
Thank you so much! So simple yet very effective!
One more thing I had to do:
Gpedit.msc: Computer Configuration | Administrative Templates | System, and disable "Turn On Virtualization Based Security".

 

OK so i had the same issue after enabling sandbox, and then disabling it . lucky i had a backup restored it and vmware works fine. so it seems enabling sandbox and the disabling sandbox caused the issue

 

I've been trying to make the most dummy proof build guide possible for work - so no Nlite and no non-MS downloads.
That's why I used the MS ISO download page (with Safari emulation to get the ISO instead of the download took) and I guess the ISO was en-US.
But all the deployment is en-GB so I hoped it would be simple to swap them over during the build but the store doesn't even work to DL the GB version and that's before I run the script to rip out all the apps etc so that's rubbish.
If there is a simple way to get the en-GB ISO of the latest Win10 I can put in this guide then great - but UUPdumps aren't going to be viable and I'm trying to avoid using MSMG as that wasn't keeping up with 1903 package removal etc and Nlite isn't free commercially.

That screenshot there is exactly what I want, though. So I guess I need the en-GB ISO somehow
If I go here using Safari user agent string to get ISO links instead of download tool links
microsoft.com/en-gb/software-download/windows10ISO
the choice is English or EnglishInternational. I don't know which counts as en-GB I'm pretty sure I used English last time and ended up with this en-US display language build.
I've just tried using the actual download tool to make an ISO and it lets me select en-GB before it downloads anything so I'm gonna see how that turns out I guess?
Anyone know if there's a way to look at/in an ISO/WIM and see if it's en-GB or not?

 

You need to login to view this posts content.

 

I've not tried the "international" version yet. Is that what I need for en-GB? If so why the hell don't they put UK like everywhere else instead of 'international'. Might end up with English (Aussie mate) or something
I've not seen a site providing such a simple bloody system to get the file you want that the adguard.net link you just gave does. Why isn't this something MS do? If that link is safe enough to use in a commercial guide (since it appears to download from MS the same as the other methods) then I could use that instead of the "go to the MS site, pretend you're safari" etc. But I guess the key for either is saying "Inter

 

English International is what you are after. Yes it is safe, the ISO files are downloaded directly from Microsoft servers.

 

Yeah I can see it is just another indexing service to provide links that MS should be providing, and less bother than UUPdumping with aria etc.
I'll spin this "international" ISO up now and see if that solves my issues. Thanks again mate. Can't believe they've made it this messy for en-GB

 

English International=EN_GB=EN_UK

Furthermore, there are three more ways to get/create the EN_GB ISO apart from the browser trick you've been using.

 

Both the US and UK use English, but as MS are American, the UK is International to them

International = United Kingdom

 

I have Win 10 Enterprise 1809 - 17763.529, and tried updating to 1903 via Windows update which fails all the time with different BSOD messages then freezes without the progress indicator updating.

So, I d/led the 1903 v1 64 bit .iso from here, and tried installing in situ from that, which got to about 61%, then yet another BSOD, but this time the error info did get to 100% then auto restarted.

The BSOD's are page faults, kernel mode, cache, etc.

I really don't want to do a clean install, unless it's compulsory, so I'm curious if anyone's had the same problems and knows a cure please?

EDIT:

I am using Comodo Firewall (no AV). Uninstalling that, allows the Windows update to proceed without errors.

 

New update downloading

 

New CU kb4503293, build 18362.175

 

can anyone run latencymon with this new build and see if the ntoskrnl spikes are still there?

 

UK colonized the globe, so it's more international