Jump to content

Windows 10 v1903 (19H1) now available from MSDN

Arthur

By Arthur
in Windows 10

 Share

Recommended Posts

Arthur

Arthur

Posted
Posted (edited)

A month earlier than expected.

 

Microsoft makes Windows 10 1903 available on MSDN

 

On 18 April, some tech pros began noticing that Microsoft had made its Windows 10 1903/May 2019 Update release available on MSDN for download. If Microsoft hadn't changed its Windows 10 servicing cadence a couple weeks ago, this would be business as usual. But, in early April, Microsoft officials said the plan was to make Windows 10 1903/May Update available to consumers and business users starting in late May, not in mid-April.

 

[...]

 

I contacted Microsoft officials to see if this was a mistake on its part or if Microsoft intended to make the coming release available a month or so ahead of schedule for those with MSDN subscriptions.

 

Update: It's increasingly looking like this was not a mistake, but intentional. In early April, Microsoft officials never shared when they planned to release the 1903/May Update bits on MSDN. In the past, Microsoft usually released RTM bits to MSDN around the same time they went to VLSC and other "mainstream" business channels. But it looks like Microsoft is going with the literal definition of MSDN -- Microsoft Developer Network -- and not looking at it as a business/IT pro channel. And so 1903's release on MSDN is tied to the SDK release today.

 

Microsoft released the Windows 10 Software Development Kit (SDK) for the May 2019 Update on April 18 with a "go-live" license and told developers they could start developing on the Windows 10 May 2019 Update now.

 

https://twitter.com/teroalhonen/status/1118955994871140352

 

dwG3pU.png

Edited by Arthur
  • 5 weeks later...
DrCheese

DrCheese

Posted
Posted

If you're a madman like I am and have already used the MSDN iso for testing, the md5 sums match up for the VLSC release and the MSDN release.

 

 

[ATTACH]53513[/ATTACH]

 

(Image is small, don't know why!)

3s-gtech

3s-gtech

Posted
Posted
Is the International English version on VLSC definitely the right one? Just installed it over the top of my International English 1703 install and US English has raised it's head.
Arthur

Arthur

Posted
  • Author
Posted
Is the International English version on VLSC definitely the right one?

That's strange. International English has always been 'en-GB' rather than 'en-US'.

3s-gtech

3s-gtech

Posted
Posted
Could just be me. However, I'm 99% sure I installed it onto my custom image built from 1703 International, and it stated it was going to change the display language upon installation. En-US has since appeared. Have they flipped them, or are both En-US (they've pulled that trick before!)?
CHiLL

CHiLL

Posted
Posted

I've been using English International for years, but I have had to configure Unattended.xml to change the primary language from en-US to en-GB in them all. I've had to do that for 1903 too.

 

I'm having an issue on my test workstation with drivers (I assume), which is causing the PC to get stuck in a "Why did my PC restart?" boot loop during the TS (after ConfgMgr has been installed). I disabled all drivers, applications and customisations in the TS and it installed fine. Now I'm working through the extras one by one to find which stage of the TS is causing the problems. I do assume it's driver related, though I'm not ruling out applications like Visigo which hook into the system, etc.

Semple1

Semple1

Posted
Posted

Does 1903 ISO language pack still exist? I read that they are changing it to App Store downloads only but the screenshot at the top shows it?

Did anyone download it if so?

Arthur

Arthur

Posted
  • Author
Posted
Have they flipped them, or are both en-US (they've pulled that trick before!)?

Just to double-check, but is this the ISO you are using?

 

[b]MSDN[/b]: en-gb_windows_10_business_editions_version_1903_x64_dvd_4170a06f.iso
[b]VLSC[/b]: SW_DVD9_Win_Pro_10_1903_64BIT_Eng_Intl_Pro_Ent_EDU_N_MLF_X22-02892.iso

   [b]MD5[/b]: 073f10ee7b8ee8c91db78b08ae4ff6c5
 [b]SHA-1[/b]: 3df67db9f9e8f181644b0503dfb2fee385570e32
[b]SHA-256[/b]: acc1571dd1b478d565113231cc47187ef49793d980b8d827976d8ec30b68e78a

3s-gtech

3s-gtech

Posted
Posted
Yup, that one. It’s more than possible it’s something this end, just seems very odd as I didn’t build my WIM with the US version of 1703, so no idea why it showed the change of language. Do you get the language change notification if running it as an upgrade (if you have something to quickly try it on - you don’t need to complete the install)?
3s-gtech

3s-gtech

Posted
Posted
This displeases me 🧐 plus my upgrade install really did reinstall ALL THE THINGS and I mentally cannot face the effort of building a custom WIM and deploying that again. Going to have to gen up on scripting the bundled shovelware to be removed post-install (yeah, I really want Solitaire going out, and having to Applocker it!)
lancia

lancia

Posted
Posted
Has anyone got problems with mapped drives through GPO. It seems that windows 1903 is ignoring the first entry. All other drives map correctly. If i move another drive to position 1 then that drive is no longer mapped. I've tested this on 3 1903 pc's and then on my 1809 ones. The 1809 ones map every drive as the same user. Hmm...
Garacesh

Garacesh

Posted
Posted
Has anyone got problems with mapped drives through GPO. It seems that windows 1903 is ignoring the first entry. All other drives map correctly. If i move another drive to position 1 then that drive is no longer mapped. I've tested this on 3 1903 pc's and then on my 1809 ones. The 1809 ones map every drive as the same user. Hmm...

 

How're you mapping them? We use the Profile tab of the user to Connect $Letter to $Path and that's mapping fine.

 

Issues here is that the start menu won't open at all (even for a user who no profile location set in AD)

Not sure if it's a start menu redirection thing or...

 

(also Edge is pinned to the taskbar, but I assume that's just a reg key tweak to fix)

ifarmery

ifarmery

Posted
Posted (edited)

 

Issues here is that the start menu won't open at all (even for a user who no profile location set in AD)

 

 

Got this same issue, i was thinking it was group policy or even applocker but haven't figured it out yet

Edited by ifarmery
ifarmery

ifarmery

Posted
Posted

- - - Updated - - -

 

Got this same issue, i was thinking it was group policy or even applocker but haven't figured it out yet

 

Sussed this, you need to allow Microsoft.Windows.StartMenuExperienceHost.exe in the packaged app of AppLocker

  • Thanks 2
Garacesh

Garacesh

Posted
Posted
- - - Updated - - -

 

 

 

Sussed this, you need to allow Microsoft.Windows.StartMenuExperienceHost.exe in the packaged app of AppLocker

 

That one doesn't show in my AppLocker list?

I assume I need the latest admx files, but I can't seem to find them anywhere.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing


×
×
  • Create New...