[1903, au] Windows 10 v1903 (19H1) now available from MSDN

[gmonks]

ADMX files usually don't get published until a little time after release. I guess we'll have to wait a few weeks yet.

[Arthur]

That one doesn't show in my AppLocker list?

Are you editing your AppLocker GPO on a PC running 1903 or from an older version of Windows 10?

 

I don't think it's ADMX-related.

Edited May 23, 2019 by Arthur

[Semple1]

ADMX files usually don't get published until a little time after release. I guess we'll have to wait a few weeks yet.

 

Can you get newer versions here after installing 1903?

 

C:\Windows\PolicyDefinitions\

[ifarmery]

I picked it off a machine running Windows 10 1903 and group policy editor.

[Arthur]

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)?

I got to the following screen and didn't get any prompts about language. Like free780 mentioned, your PCs may have downloaded the en-US language pack.

 

 

If I run the following three PowerShell commands I only see en-GB listed.

 

Get-Culture
Get-UICulture
Get-WinUserLanguageList

 

LCID             Name             DisplayName                                                                                                                                                                                                                    
----             ----             -----------                                                                                                                                                                                                                    
2057             en-GB            English (United Kingdom)                                                                                                                                                                                                       
2057             en-GB            English (United Kingdom)                                                                                                                                                                                                       

LanguageTag     : en-GB
Autonym         : English (United Kingdom)
EnglishName     : English
LocalizedName   : English (United Kingdom)
ScriptName      : Latin script
InputMethodTips : {0809:00000809}
Spellchecking   : True
Handwriting     : False

[free780]

If you using WSUS or SCCM SUP.

 

https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Updating-Windows-10-version-1903-using-Configuration-Manager-or/ba-p/639100

 

I wonder what UUP will involve. Since Windows 10 was release MS have been trying to get organisations to use delivery optimization and Windows Updates for Business. Basically delaying updates and using client devices as peer content sharing.

[Arthur]

my upgrade install really did reinstall ALL THE THINGS

Which version of windows 10 were you upgrading from? Was it 1703 or 1709? If so, that might explain why that happened.

 

How to keep apps removed from Windows 10 from returning during an update

 

When you update a computer running Windows 10, version 1703 or 1709, you might see provisioned apps that you previously removed return post-update. This can happen if the computer was offline when you removed the apps. This issue was fixed in Windows 10, version 1803.

 

When you remove a provisioned app, we create a registry key that tells Windows not to reinstall or update that app the next time Windows is updated. If the computer isn't online when you deprovision the app, then we don't create that registry key. (This behavior is fixed in Windows 10, version 1803. If you're running Windows 10, version 1709, apply the latest security update to fix it.)

 

Note. If you remove a provisioned app while Windows is online, it's only removed for new users—the user that you signed in as will still have that provisioned app. That's because the registry key created when you deprovision the app only applies to new users created after the key is created. This doesn't happen if you remove the provisioned app while Windows is offline.

[3s-gtech]

1703. Yup, that explains it. Hey, this Summer update is going to be an unfeasible nightmare anyway, so having to run a PS script I found that removes the apps post update, won’t worry me any extra.

[CHiLL]

We're running Impero 7.4.36 and that is installed as part of the TS (along with other essential software) and I've found that when Impero installs, it causes 1903 to get stuck in a boot loop. I'm waiting for Impero to upgrade my available version to 8.0.64 so I can use that instead in the TS and see if the problem still exists.

 

Edit: Come to think of it, I've installed 1903 on my workstation and using Impero 7.4.36 without issues. I've just manually installed Impero on the test workstation I removed Impero from the TS for and it's also working fine (and reboots fine). Unless it's an issue with installing Impero during the TS? I'm still working on it.

Edited May 24, 2019 by CHiLL

[free780]

I uninstall Impero in upgrade task sequences. Then install at the end.

[CHiLL]

We're running Impero 7.4.36 and that is installed as part of the TS (along with other essential software) and I've found that when Impero installs, it causes 1903 to get stuck in a boot loop. I'm waiting for Impero to upgrade my available version to 8.0.64 so I can use that instead in the TS and see if the problem still exists.

 

Edit: Come to think of it, I've installed 1903 on my workstation and using Impero 7.4.36 without issues. I've just manually installed Impero on the test workstation I removed Impero from the TS for and it's also working fine (and reboots fine). Unless it's an issue with installing Impero during the TS? I'm still working on it.

Since upgrading to 8.0.64, the issue has gone. So it appears that 1903 doesn't like at least 7.4.36 of Impero.

[browolf]

Updated to 1903 yesterday. Noticed these issues today.

 

The keyboard locale reverted back to US - Couldn't type £s.

 

The server admin tools are gone - Apparently it's no longer a download. but an optional windows "feature" except it doesn't show up in windows features.

I had to use this powershell script instead. https://gallery.technet.microsoft.com/Install-RSAT-for-Windows-75f5f92f

 

to get the script to run.

set-executionpolicy unrestricted

 

You can revert it to allsigned afterwards

Edited June 4, 2019 by browolf

[Arthur]

Has anyone come across the following bug in 1903?

 

Right-click This PC in File Explorer and then select Manage.

 

When I do this it opens Server Manager instead of Computer Management.

 

[3s-gtech]

Hmmm, I don't get Computer Management loading - but I don't get anything loading. I guess it's trying to load Server Manager, like yours, but it's not present on the install so nowt happens. Doesn't bother me that way - Win+X works.

[ollyyllo]

It looks like this update kb4503293 from June 11th fixes the issue.

Doesn't say anything about it in the notes, but after installing it Computer Management now opens up when I click Manage.

Edited June 12, 2019 by ollyyllo

[Arthur]

Thanks @ollyyllo. I will give that a try.

[computer_expert]

Get the same on my 1903 build (upgraded from 1809 via WSUS) although I can't remember if I enabled server manager via RSAT...

[Arthur]

Spotted this on r/SCCM.

 

Removing Microsoft.MicrosoftSolitaireCollection will break your Windows 10 Version 1903 Image

 

When using DISM or PowerShell to remove unwanted built in Windows 10 Apps from you WIM File, you will break the Photos, Movies & TV, Screen & Sketch, Get Help and Camera App for all new user profiles signing on after upgrading from Windows 10 Version 1809 to 1903.

 

You can't start those mentioned apps on any new user, they are listed Start Menu but clicking on it will result in neither an error message nor anything happening at all.

 

You can also not just use Add-AppXPackage to reinstall those Apps, as you will receive "The system cannot find the path specified".

 

All profiles already existing on 1809 will be fine and those Apps will work as expected.

[DrCheese]

ugh, I nearly came to the same conclusion regarding removing apps when I was having trouble with the new photos app not showing the video editing tools. If Microsoft just let you hide certain built in apps (xbox etc...) from the start menu I don't think we'd all be trying to gut them out of the default image. Yes, applocker works perfectly but those of us that are OCD would rather they not appear in the first place...

[3s-gtech]

Glad I’ve done it the post install way this time. Still yet to test in anger - don’t want early September to be the beta phase!

[CHiLL]

Spotted this on r/SCCM.

 

Removing Microsoft.MicrosoftSolitaireCollection will break your Windows 10 Version 1903 Image

The post on Reddit says that affects upgrades from 1809 to 1903. Does anyone know if this affects clean installs?

[DrCheese]

Doesn't affect clean installs no (My image has it removed) - But it may affect going from 1903 to 1908/9 later in the year..

[BOOT]

Had this issue in v1803. Nice to finally know the cause.

[Garacesh]

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.

 

Are you editing your AppLocker GPO on a PC running 1903 or from an older version of Windows 10?

 

I don't think it's ADMX-related.

 

Do we know that this is definitely the case?

I've ripped the ADMX/ADML off a 1903 install but still don't have Microsoft.Windows.StartMenuExperienceHost.exe in the AppLocker list.

[ifarmery]

I had to edit the GPO on a machine running the Microsoft.Windows.StartMenuExperienceHost.exe so that it could be picked from the list.

 

It definitely fixes the lack of start menu issue