BOOT

...one minute later.

Have you enabled the [Allow deployment operations in special profiles] policy? in: Computer Configuration\Administrative Templates\Windows Components\App Package Deployment

Did you remove any preinstalled apps?

1280x1024 and 1920x1080 in PNG format. Refreshed with a powershell script on startup.

Powershell script I use: New-Item -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\bootim.exe" Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\bootim.exe" -Name "Debugger" -Type "String" -Value "taskill /F /IM bootim.exe" -Force Easily undone if you need to access those options.

They won't build from the same deployment a second time. The PXE boot log will show "Already in database" "No deployments available".

Are the GPO permissions correct?

@sydborn, By "Start Menu customisation" I'm referring to Start Menu tiles customisation via XML files.

Things I found: Roaming profiles are "unsupported and may be removed in a future version of Windows". Start Menu customisation is broken with roaming profiles; as with roaming profiles the data is stored in a "Cloud Store" and intended to be sync'd (via Microsoft Account\Enterprise State Roaming\etc). The "Delete user profiles older than X days" policy is very much broken; as the profile receives updates on startup\sync\etc and never appears as old enough to delete. Even with 1909 it all still seems to be a "work in progress".

...And it's scripts like that which cause so many problems with UWP Apps.

The snipping tool is still in 1909, though it does now tell you it's going away in a future update.

Don't use Remove-AppxPackage. It will break other apps. Use Remove-AppxProvisionedPackage. This stops the app being auto-installed on first\subsequent logons.

Looks like the .swf is encrypted. Might be related to this: http://www.northcode.com/blog/SWF-Studio-and-Windows-10

Blocked by Anti Virus software? It was a known issue a while back.

I run it twice, seems to sort that issue second time around.

Never run Remove-AppxPackage. It causes more harm than good. Only use Remove-AppxProvisionedPackage. Use Local profiles. Use only Education or Enterprise. Get used to UWP Apps becoming the norm - even Notepad is a UWP app now.

It'll run in the RM Service Host user account. Look for a folder in C:\Users something like [sitecode] [random]@[domain]

If you want to disable it completely... Little bit of powershell: New-Item -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\bootim.exe" Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\bootim.exe" -Name "Debugger" -Type "String" -Value "taskill /F /IM bootim.exe" -Force

I don't think I've ever seen them use any apps other than web browser and camera...

Looks like a hybrid system - Combi boiler feeding a storage tank for power-shower. Could just be a stuck mixer valve, only letting mains cold water in and not water from the boiler. It'd still heat up on a timer via the boiler loop, just not get topped up. When shower etc is used, it'll only fill up with cold water.

I found setting the computer GPO option [system/User Profiles/Only allow local user profiles] for my new Window 10 builds very useful when migrating. Allows roaming profiles to be used on PCs without that GPO set, switches to local profiles where the GPO is enabled.

If you're running the network version, have you also installed: \Workstation Setup\LucidUniversalThinClient.msi (Probably in the Lucid Exact share)?

Both 32 AND 64 bit versions of the Microsoft SQL Server 2008 R2 Native Client installed?

Is any part of it working? None of my layouts start with: Try it without maybe?

Unless you're pinning UWP Apps, AppUserModelID should be DesktopApplicationID It is perfectly fine to point to the .exe On 64 bit PCs: {7C5A40EF-A0FB-4BFC-874A-C0F2E0B9FA8E} is for [Program Files (x86)] {6D809377-6AF0-444B-8957-A3773F02200E} is for [Program Files] Unless you're pinning UWP Apps, TaskbarPinList entries should use: