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

Anonymous
2024-12-16T16:39:34+00:00

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:

  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.

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:

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

  1. Disable Secure Boot on your PC.
  2. Then get into Windows Recovery, choose advanced boot options and disable driver signature enforcement.
  3. Then do the above-mentioned workaround for deleting the policies after logging in.
  4. Alternatively, you can also delete the above-mentioned policies directly from the Windows Recovery console.
Windows Insider program | Windows Insider preview | Install, activate, and Windows update

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 No comments

91 answers

Sort by: Newest
  1. Anonymous
    2024-12-30T19:24:50+00:00

    For me, it keeps showing "Could Not Find S:\EFI\Microsoft\Boot\cipolicies\active{8E8A94F0-6EB9-42C7-A189-E018C8CF3D10}.cip"

    Any workaround to this? This issue has been really problematic for me as 3rd party apps aren't opening, and my touchpad and keyboard isn't working.

    Thanks

    You can check if the EFI partition is really mounted and if the files are present or not.

    after mountvol S: /s is succesfull enter S: to select the S: volume.

    then

    cd EFI\Microsoft\Boot\cipolicies\active

    then

    dir /a /s

    that should display if those 3 files are there or not.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-12-30T15:36:00+00:00

    For me, it keeps showing "Could Not Find S:\EFI\Microsoft\Boot\cipolicies\active{8E8A94F0-6EB9-42C7-A189-E018C8CF3D10}.cip"

    Any workaround to this? This issue has been really problematic for me as 3rd party apps aren't opening, and my touchpad and keyboard isn't working.

    Thanks

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-12-30T08:35:23+00:00

    @Mauricio Galiana,

    The reason it fails is because you did not mount the EFI partition as S:

    (unidad: /s in your case should be S: /s) 😉

    Before trying to delete the files, issue the command:

    mountvol S: /s (This will mount the EFI partition as Volume S:) After that you can issue the del commands that follow and then reboot.

    The instructions on the 1st Post are pretty clear, but you did not follow the instructions step by step. 😎🤷‍♂️

    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.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-12-30T08:08:27+00:00

    al poner las series dice: El sistema no puede encontrar la ruta especificada

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-12-30T01:31:13+00:00

    This was exactly my case. No keyboard and no wireless mouse. So frustrating, I had to pause several projects for 4 days. Good thing I didn't reinstall everything! Even better, I didn't listen the message saying to call my IT department and accusing them of pushing group policies on my personal PC.

    Not only that the Canary channel is a problem, but I start trusting MS less and less. So intrusive! Microsoft, you cannot do that and wait 4 days to notify users or find a fix!!!

    Don't use a Canary build if you are not ready to deal with issues... there is no "Canary channel" problem, there is probably a misunderstanding problem.

    I have no clue what misunderstanding are you talking about. I am subscribed to Canary and I have no issue dealing with computer issues, in general. This time, the problem was that an update locked me out of my laptop and a message was telling me (wrongfully) to call my IT department for a fix. Then it took 4 days for Microsoft to acknowledge the problem and let it's users know about the fail! I forced tens of cold restarts trying to get my access back, which could have damaged the HDD (if you know anything about computers).

    Was this answer helpful?

    0 comments No comments