thatley

Rolled out 20H2 fresh from WDS at a school last week (65 machines) and all working well. Only issue I had was the new embedded MS Edge Chromium adds Online Office Apps shortcuts to the start menu when you run it, which is typical MS and annoying. Created a GPO to delete those shortcuts for each user, so they never see them. Apart from that, all good!

Basically this reg key gets created if you toggle the "settings" to off in the Notifications & Actions screen. I just use a GPO to disable the "settings" notifications enabling that reg key so you don't get the messages on first logon (new profile). So to clarify, with the "settings" notifications disabled, none of those messages will appear at first logon, but the 'defaultassociations.xml' still doesn't kick in until the user logs off and on again.

Hi, On first log on to a machine, you get the messages and it doesn't change the defaults from the .xml. Log off then on again and .xml settings kick in. I think this has done this since 1803 what I can remember.

I found this on 1903 but you only seem to get 3 of the messages but that's only at first logon. With 1909, you get 12 messages which is ridiculous. Found this with older version of xml or a new one. I worked around this by disabling only the "system" messages in the action centre with a GPO that changes this REG_DWORD setting: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Notifications\Settings\windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel\ Set value to 0 Not had any issues so far, so keeping it until it gets fixed (if ever!)

Cheers Arthur, In our office, no Applocker at all so that's not an influence. Also it gets fixed by deleting profile so the symptom would've returned if that was the case. It's certainly a strange one and hoping that it will be either a file issue/replacement or an MS fix. I've reported it on the Feedback Hub and so have a number of people, so hopefully it will gain momentum. I'm also hoping someone can re-create this who reads the forum.

Hi, I'm wondering if anyone has come across this and fixed it without having to delete roaming profiles. I've had this on all four machines I've upgraded from either 1803 or 1809 to 1903 using WSUS or the Windows Updater Tool. This is only in my office at the moment, but worried about all the schools we support on Windows 10 when they update this year and next from 1803. We and they, all have roaming profiles so this could be a big issue. After the upgrade these are the symptoms: - Action Centre doesn't open when you click on it - Right click on it and select 'Open Action Centre' does nothing - In 'Settings, Notifications & Actions', nothing happens when you click on 'Edit your quick actions' - Notifications do pop up, but you can't open them to read them and the badge number just accumulates because you can't read them - The error in the Event Viewer when you try to open the Action Centre is this: Faulting application name: ShellExperienceHost.exe, version: 10.0.18362.145, time stamp: 0x5ce50c77 Faulting module name: ucrtbase.dll, version: 10.0.18362.1, time stamp: 0x5cbddb81 Exception code: 0xc0000409 Fault offset: 0x000000000006d3be Faulting process ID: 0x510 Faulting application start time: 0x01d53b0858a9b62e Faulting application path: C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report ID: d0866835-c81b-4dd0-a3e8-96a0223c8574 Faulting package full name: Microsoft.Windows.ShellExperienceHost_10.0.18362.145_neutral_neutral_cw5n1h2txyewy Faulting package-relative application ID: App I've tried pretty much every fix that I've googled but none of them work (renaming the 'UsrClass.dat' file in the local profile, changing transparency settings, re-starting explorer.exe, disabling and enabling items in 'ShexView'). I'm now at a loss to fix this. The only fix was to delete the local and roaming copy of the profile and that got it to come to life. All existing profiles are broken, so another quality update from Microsoft as usual!! Anyone?

No worries GShaw, glad this post helped. I too have had many issues fixed due to this forum - it's invaluable!

Yes I always notice that after about 10 machines have started to build, then boot.wim slows right down anyway. And you are right, the old days of DVD's/Ghost etc are well and truly behind us

For information: This "workaround" (sorry, I said "fix" in my previous post), does slow down the loading of the boot.wim file. I've only tested this on a single machine, so not sure how slow it will be when building a large number of machines.

UPDATE: Microsoft have now acknowledged this in their online update support pages. Message below: "After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension." The fix is much easier than removing the updates: “Use the Windows Deployment Services UI. 1. Open Windows Deployment Services from Windows Administrative Tools. 2. Expand Servers and right-click the server name. 3. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab. 4. Restart the WDS Service. 5. If that doesn’t work, you may need to restart the server. Microsoft is working on a resolution and will provide an update in an upcoming release." Good luck!

In case any of you come across this - this may save you some time. Issue: When building machines from WDS you get this error at the point the Boot.wim tries to load - "Windows failed to start. A recent hardware or software change might be the cause........" If you click past this screen you'll see the boot image and if you choose it, it loops back to this point every time. This affects Server 2016 and Server 2012 (possibly 2008 R2 but I've not confirmed this yet.) The problem is a cumulative update/s from Microsoft this week: • KB4489882 for Server 2016 (tested removal on a number of servers and it fixes the issue) • KB4489881 and KB4489883 for Server 2012 The 2008 R2 updates are: • KB4489878 • KB4489885 The problem is one of the updates patches a security hole in TFTP, but unfortunately breaks WDS. Hopefully MS will fix this asap! Advice is to decline the update/s in WSUS and then uninstall the relevant update/s. You will have to reboot after removal so bear this in mind. Hope this helps anyone seeing this issue.

Going to do that now. Thanks for your help. PS, how do you like to product?

Thanks. I've just had a reply back from Atomwide about the ports and 443 is open. They suggest URL's may need to be allowed, but I'm not sure that would just block the Remote Desktop aspect. My trial started yesterday which is the brand new released version - i wonder if it's anything to do with that.

Hi, I know this is an old thread, but I'm just going through a trial with Pulseway now and hoping to replace the ever price increasing Centrastage! From what I've seen already, it's a fantastic, powerful bit of software and really impressed. Only trouble so far is that Remote Desktop isn't working. They say it's because port 443 is not open outbound from my end, which i'm pursuing now with the LGFL (but I'm sure it's open!) Did you have any issues with your setup? Thanks

Yes I reported this back on page 3 of this thread - I'm staying well clear of 1809!

Classic Windows 10 Microsoft!! Don't worry, staying well clear for at least a couple of months. Sticking with 1803 for now, which is relatively stable but has quite a few quirks still. Thanks for the warning though.

Also discovered it 'Red X's' any mapped drives every logon. Here we go.........

Thanks Arthur. Without sounding like a total pessimist, lets see what they've broken in this release!

Cheers for the information Arthur - Interesting to know.

Exactly the same issue here on Edu 1803. Reg entry is in place after enabling the policy but nothing syncs either way. I've tried it as a user policy and computer policy - no change. Anyone had any joy with this?

Just a quick update on the "Missing Apps with Roaming Profiles". I know it's early, but I've been testing 1803 this week and fingers crossed, it looks like this might be fixed. On first logon, you don't seem to get all the apps, but log off, or restart (on restart our local profiles get deleted by delprof) log back on and all apps are there and seem to stay no matter what. It's early days, so I'll keep you updated either way. For those of you that use Classic Shell still - works absolutely fine in 1803 too.

Nooooooooooooooooo! Well I'm on a big install at a school this week and next installing my 1709 build, so don't have time to look at that. If anyone does look at it in the meantime, please report back if the issue is fixed or not. Thanks Arthur.

Nothing yet and I've been looking at every update released so far (see here): https://support.microsoft.com/en-gb/help/4043454/windows-10-windows-server-update-history Looking at the update history, they seem to break more things than they fix. Pi$$es me off too - I don't know how seriously MS has taken it but I hope they do something soon!

Sorry was being thick! Got this to work - you genius! Cheers buddy

Thanks for this, looks promising too EDIT: Just used your entry and the script from your link - works MINT! Thanks so much for this!!!