I'm having an issue where Windows 10 is prelaunching Microsoft.Photos in the background which causes some state test assessment software to not function because that's a potential cheating violation:

I've had this happen years ago but it was resolved by disabling App Prelaunch. However, app prelaunch is already disabled on these computers (and has been for years via group policy) yet I'm still getting this behavior:

This is the only user logged into the computer and of course I've already tried logging off and on and rebooting. Sometimes the app doesn't preload but often it does and I don't know why.
This occurs in a computer lab and it seems kind of random if photos prelaunches or not. It happens on various builds of 20H2:
Name OSVersion PhotosRunning
---- --------- ------
MV-LAB2-01 10.0.19042.928 Yes
MV-LAB2-20 10.0.19042.928 Yes
MV-LAB2-24 10.0.19042.928 No
MV-LAB2-28 10.0.19042.928 Yes
MV-LAB2-30 10.0.18363.1082 No
MV-LAB2-31 10.0.19042.928 No
MV-LAB2-45 10.0.19042.867 Yes
Any ideas why Windows isn't honoring the disabled app prelaunch setting (anymore)?