Fixed with 27766 Workaround for “Your organization used App Control for Business to block this app” dialog in the Canary Channel

Anonymous

After updating to Build 27764 in the Canary Channel, some Windows Insiders are reporting hitting the issue that previously impacted the Dev Channel where an “Your organization used App Control for Business to block this app” dialog is shown when attempting to use or install certain third-party apps on your PC due to an incorrect policy being enforced. The following steps should mitigate the issue:

Open Command Prompt with administrator privileges.
Type and hit enter: mountvol s: /s
Type and hit enter: del S:\EFI\Microsoft\Boot\cipolicies\active{8E8A94F0-6EB9-42C7-A189-E018C8CF3D10}.cip
Type and hit enter: del S:\EFI\Microsoft\Boot\cipolicies\active{36D62F7C-AB85-4F61-8724-744294F24023}.cip
Type and hit enter: del S:\EFI\Microsoft\Boot\cipolicies\active{66D7D265-7EDD-47DD-86E4-F7C42CD55A8F}.cip
Then reboot your PC.

If you are dual-booting between the Canary Channel and the Dev Channel or another version of Windows, you will need to do this workaround BEFORE booting to the other OS.

If the above steps do not work, you may need to disable Secure Boot first and follow these steps:

Disable Secure Boot on your PC.
You will be asked to enter your BitLocker recovery key.
Log in to your PC and open Command Prompt with administrator privileges.
Type and hit enter: mountvol s: /s
Type and hit enter: del S:\EFI\Microsoft\Boot\cipolicies\active{8E8A94F0-6EB9-42C7-A189-E018C8CF3D10}.cip
Type and hit enter: del S:\EFI\Microsoft\Boot\cipolicies\active{36D62F7C-AB85-4F61-8724-744294F24023}.cip
Type and hit enter: del S:\EFI\Microsoft\Boot\cipolicies\active{66D7D265-7EDD-47DD-86E4-F7C42CD55A8F}.cip
Reboot your PC once with Secure Boot still disabled.
Then reboot again and enable Secure Boot.

In small cases, your PC may not boot into Windows. To get out of this state, you can follow these steps:

Disable Secure Boot on your PC.
Then get into Windows Recovery, choose advanced boot options and disable driver signature enforcement.
Then do the above-mentioned workaround for deleting the policies after logging in.
Alternatively, you can also delete the above-mentioned policies directly from the Windows Recovery console.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

91 answers

Anonymous

2024-12-17T05:53:38+00:00

I wish I had seen this last night. I first noticed problems when my keyboard and touchpad suddenly didn't work after an update, then got the "app control for business" thing after trying to restore the PC and uninstall a McAfee program that apparently came preinstalled with the Laptop, which had Windows 10 on it when I bought it several years ago. I managed to find another post here related to this about how to delete the policy using citool, but of course got an error indicating I didn't have permission to do that when I tried it. I also ran into a similar issue when using command prompt from the recovery options to mount the EFI partition and delete the contents of the EFI folder, which was another suggested fix. Finally ended up booting into Linux since I have a dual-boot setup, then used a partition manager program to reformat the EFI partition and finally reinstalled Windows from a USB drive.

Definitely not going to go with the Canary channel anymore. Sticking to the standard public release for now until I get everything reinstalled and working properly.
Was this answer helpful?

0 comments No comments
Anonymous

2024-12-17T00:34:16+00:00

A little too late for me. 😵‍💫

This problem screwed up my dual boot system (on Dell XPS 8930), that had Public Build 24H2 26100.2605 on the main disk and Canary 27764.1000 on a second disk drive.

Both systems were showing errors in device manager and various components including my Ethernet Killer E2400 were not working at all.

I also tried a clean install of 27764 and ended up with the same issues.

At the end I just did a clean install of 26100.1742 to get the system up and running again

Now I have my main system using 26100.2605 public build and the dual boot on the second system with 26100.2605 in the R.P. insider channel. Everything seems back to normal after reinstalling all the programs that I had before.

I'm not going to try 27764 again on this machine.

I hope MS will fix this mess on the next Canary build.

This was really a wasted weekend. 🤬🤷‍♂️
Was this answer helpful?

0 comments No comments
Anonymous

2024-12-17T00:28:43+00:00

You won't believe what I have been through for the last week, trying to fix this bug.

I can't believe that it took only three lines of commands to solve this problem.

Why does Microsoft put their users in such a terrible situation, by sending updates that affect the computer in such a way that nothing is working, and don't fix it ASAP?

I ended my journey by buying a new laptop after I couldn't work and tried everything in my power to find a solution, with no luck.

<Removed>
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2024-12-16T20:34:55+00:00

Many thanks worked for me
Was this answer helpful?

0 comments No comments
Anonymous

2024-12-16T18:24:38+00:00
This worked for me

Thank you .
1. Open Command Prompt with administrator privileges.
2. Type and hit enter: mountvol s: /s
3. Type and hit enter: del S:\EFI\Microsoft\Boot\cipolicies\active{8E8A94F0-6EB9-42C7-A189-E018C8CF3D10}.cip
4. Type and hit enter: del S:\EFI\Microsoft\Boot\cipolicies\active{36D62F7C-AB85-4F61-8724-744294F24023}.cip
5. Type and hit enter: del S:\EFI\Microsoft\Boot\cipolicies\active{66D7D265-7EDD-47DD-86E4-F7C42CD55A8F}.cip
6. Then reboot your PC.
Note the first command is Type and hit enter: mountvol s:/s
Was this answer helpful?

0 comments No comments