I recall a case I ran into during a Win10 IPU (1809 to 1909, maybe) where an app had an invalid autorun reg entry that was somehow getting "cleaned up" during the IPU. This caused the app to think it needed to be "repaired" on next run. Only thing that comes to mind of an app being damaged post- IPU

The pw reqs are all disabled (except for 4 char limit which can't go lower) but shouldn't be a factor anyway if removing/setting back to nothing. It works to remove it in the BIOS GUI so that's the only workaround I've found so far. Prob need to open a support case 😩

For old models at least, a pw needs to be set for the TPM related commands to work IIRC. Probably not the case for newer models but the TS is 1 size fits all and the device tail is long. Could rework but hasn't been a reason to until now

youtu.be/jJzki0inKBk

Let's say an org was using ConfigMgr + MDT task sequences, including an MDT database that contains all the make model (drivers/BIOS) and role (packages/apps) info...would DeployR be able to replace that? This is purely hypothetically speaking, of course... 😅

Wow, this takes me back...I loved playing with Construx! I remember trying to make a wearable Ghostbusters proton pack out of them long ago 😄

A possible workaround is setting Software\Microsoft\Windows\CurrentVersion\DesktopSpotlight\Settings\EnabledState = 0 in the default user hive. Still testing.

Same workaround 10 years later as well? www.deploymentresearch.com/fixing-why-s...