Screwed up with GPO, now it cannot apply the "AppV" & "UEV" Policy.

Long story short, I upgraded from Window 10 HOME to Window 10 PRO via Settings -> Update & security -> Activation -> change product key. And all went fine.

Since it is now new to me I've been checking out the Group Policy Editor and I noticed two new things that were not part of HOME Edition before, "App-V" (Microsoft Application Virtualization (App-V)) and "UEV" (User Experience Virtualization (UE-V)).

Since these both seem to be about virtualization and server type management stuff, stuff I don't use nor plan too, I set both Policies for them to disable. "Enable App-V Client" and "Enable UEV" respectively.

But now on every reboot I've been noticing two new warnings in Event Viewer;

Windows failed to apply the AppV Policy setting...



Windows failed to apply the UEV Policy setting...




As an "oops, I'll fix this" I undid the two Policies I set as disable "Enable App-V Client" and "Enable UEV" back to their original state to "Not configured", but these warning still persist every time I reboot my system. It looks like GPO is trying to apply these two settings even though I don't have or use these two features. They might not even be something that's installed or supported by my machine (which is pretty old)...

How can I fix these warnings? Is there a way to have GPO stop trying to apply these two rules on every reboot?


And if this is helpful or relevant:
Windows version 1909
OS Build 18363.1440

Group Policy Management is a feature reserved for the Professional, Enterprise, and Education editions of Windows.

You can execute an attached script to reset group policies apply to your computer.

Can you tell me what the bat file does? I've already tried resetting GPO by renaming the folder "Machine" to "Machine.old" located at;

"C:\Windows\System32\GroupPolicy\Machine"

and following that up with gpupdate /force cmd, the error though still persists on reboots.

After a month of frustration trying to resolve this issue on some Windows servers, I finally figured it out. You must delete all numbered keys under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\History\{2BFCC077-22D2-48DE-BDE1-2F618D9B476D}.