×
×
×
×

Patch Already Installed

Last Updated On: 18 May 2026|
4 minutes read |

When trying to install a Windows BIOS or a Feature pack Update, you may see the following errors:

  • Patch already Installed and the changes will not be effective until the system is rebooted.
  • Patch installed successfully, but rolled back on reboot.
  • Feature Pack Rollback Issue
  • Alternative Steps for Encryption Software

    • BIOS Rollback Issue

    After deploying a BIOS update and restarting the machine, the BIOS version remains unchanged and still shows as "missing". The BIOS update was sent successfully, but:

    • Another process (like a Task Update or security tool) may have interrupted it.
    • The system was not plugged into power.
    • BIOS switch arguments were not used properly.

    Resolution

    1. Ensure device is plugged in. BIOS updates will not proceed unless the device is connected to a charger.

    2. Restart the computer. If the device had other updates applied recently, reboot it before attempting the BIOS update.

    3. Deploy BIOS using vendor-specific command-line switches (Dell). Run the BIOS update manually using these switches: /s /l=bios-upd.log /f

    4. Avoid installing other updates with BIOS. Do not combine BIOS update with other patches or updates in the same task.

    Feature Pack Rollback Issue

    The Feature Pack update was deployed, but after rebooting, the system rolls back to the previous version. This may be due to

    • Antivirus or encryption software may be blocking Windows from completing the update.
    • If a patch is retried within 3 days, Patch Manager Plus’s loop prevention may block it.
    • Drivers or files required during reboot were not migrated properly.

    Resolution

    1. Try disabling or uninstalling your antivirus temporarily before retrying the Feature Pack installation.

    2. Delete loop prevention file. If retrying within 3 days, delete the following file before re-deployment: C:\Program Files (x86)\Patch Manager Plus\UEMS_Agent\logs\installed_fp_details.json

    3. Open Command Prompt as Administrator, and run: cd C:\$WINDOWS.~BT\Sources SetupDiag.exe /LogsPath:C:\$WINDOWS.~BT\Sources ; A Logs.zip file will be generated in the same folder. Share it with support.

    4. Check if Antivirus is registered by opening the setupdiagresult.log file and look for Registered AV. If it shows Windows Defender, it means no third-party antivirus is blocking. If another antivirus is listed, it must be disabled.

    Alternative Steps for Encryption Software

    If the system has encryption software (like TrendMicro, McAfee), either:

    • Temporarily disable encryption software, or
    • Use Reflect Drivers method. If disabling isn't possible, run the command with the Reflect Driver path: /auto upgrade /DynamicUpdate disable /quiet /noreboot /compat IgnoreWarning /BitLocker TryKeepActive /ReflectDrivers "C:\Program Files\Trend Micro\Full Disk Encryption\drivers". This applies only for encryption tools, not antivirus software.