v01d

Make heavy use of AppLocker's 'audit' policy so that you can test thoroughly before implementing it and when making changes going forward. That should provide you with enough of an idea if issues suddenly crop up along the way.

Just confirming your issues that I have also had issues with VLC not playing DVDs in Windows 10. I've transitioned to PotPlayer now which just works.

Glad I'm not the only one that has been combing each update's release notes for a fix to this ridiculous issue that should've been well and truly fixed by now.

Are you using MDT?

Yeah, this. Not that I've ever really needed it, but out of habit I always take one of each new device we get and use MDT to capture an OEM image, using the model as a name, which I then store for safe-keepings.

Thanks for your effort and communication Raisin! One less thing to have to stress about whether it'll ever be resolved or not.

If they are going to require us to keep a shorter life-cycle for the OS build before we need to move to the next release, then they really need to get their act together, get all of it together, put it in a box and make sure that basic things like start layouts actually continue to work consistently across the builds. My end-users having to deal with regression issues because the QA at Microsoft is a joke genuinely makes me angry.

May 2017+ updates will be listed as... YYYY-MM Security Update for Adobe Flash Player for Windows for x-based Systems (KB<#>) Older pre-May 2017 updates are listed as... Update for Adobe Flash Player for Windows for x-based Systems (KB<#>) If you click on "Search" on the right-hand side of the WSUS console you can type in "Update for Adobe Flash" to see all the updates (approved/unapproved/declined etc...) visible on your WSUS server currently.

To go along with the above tips, I would also recommend using the following maintenance script to keep things nice and clean. https://community.spiceworks.com/scripts/show/2998-adamj-clean-wsus

Create a registry entry under Computer Config -> Preferences -> Windows Settings -> Registry Keypath: SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced Value name: LaunchTo Value type: REG_DWORD Value data: 1

Same problem here. 1. Log in with a new domain user (local profiles, not roaming) and the calculator UWP app works fine. 2. Log out and log in as an admin user and delete local profiles. 3. Log back in again as the first user and trying to run the calculator app comes up with the dreaded "You’ll need a new app to open this calculator" message. If I right-click the calculator tile in the start menu and run it as an administrator it'll actually start working again. Still, this problem affects all deleted profiles, whether limited or local/domain administrator. I hope there's a fix soon.

This made me laugh way too much, way too loudly and for way too long than it should've.

I noticed this issue when doing a client upgrade task sequence from 1703 to 1709. While yet to test my theory, I wonder if it is the winapp removal script I'm running after performing the OS upgrade causing the issue. It's not entirely consistent who it chooses to impact, which is always nice. To resolve the issue, I run the below command in a powershell script ...

That. Not even a question. Thats the whole point of taking a snapshot pre-sysprep command.

This is how I picture you when reading your nightmare dealings with Win 10 and the prospect of more nightmares to come with every new build http://2.bp.blogspot.com/-1cOmrnB2bDo/UF9P0q1yZvI/AAAAAAAADIw/4jwAmABdj6g/s320/Vince-McMahon-distraught.gif Having to finally delve into Win 10 deployment myself. Fingers crossed I don't end up the same!