none
FSLogix rules preventing Windows Updates RRS feed

  • Question

  • We are seeing an issue with FSLogix rules preventing Windows updates, and specifically Office updates from running on Windows 2016 servers unless we remove the rules from the FSLOGix rules folder. Once the rules are pulled from the folder updates can run, and the rules then have to be replaced after updates.  This is a bit cumbersome for some environments that have several RD servers.  Anybody else seen this, or have ideas on what would correct this?
    Wednesday, June 24, 2020 2:54 PM

All replies

  • Have seen this because I prevented access to some All Users Startmenu folders.

    Solution: Remove the rule assignment for the user that runs Windows Update.

    Easily spotted in the log file created by Get-WindowsUpdateLog.

    Thomas


    Monday, July 13, 2020 2:17 PM
  • But what about when another Microsoft file needs to be updated the following month? I would imagine that at some point every file masked through FSLogix will need to be updated at some point. Up to and including the executable. So we need a way to blanket create an exemption for updates to work on masked microsoft products. 
    Thursday, July 16, 2020 2:35 PM
  • I had the same problem publishing Office, added System as a user with no policy applied in the app rule and it was solved
    Friday, July 17, 2020 1:33 PM