Allgemein

[SOLVED / How To] Upgrade Azure File Sync Agent from v14.1 to v15 or v16 on Windows Server 2022 (1603 error – wrong OS version)

My Windows Updates recently couldn’t update the Azure File Sync Agent v14.1 to any newer version of it (running on the lab-Domain-Controller).

Important to know: I did a Inplace upgrade from Windows Server 2019 to Windows Server 2022 on this machine, where File Sync Agent was installed. The 2019 OSBuildInfo was still on 2019 on the Agent Registry Values, so the updater „StorageSyncAgent_WS2022 v16.msi“ needed to say „not correct OS“, even the real OS was right.

So, I tried several (10?) methods:

  • Update Installation (wrong version)
  • Repair Installation (fatal error)
  • Patch Installation via cab/msp (wrong version)

What finally solved my can’t update issue (before doing the same, check the maybe root cause at the end!):

  • Run Microsoft Troubleshooter
    • Uninstall Azure Storage Sync Agent
  • Delete the service
    • Sc delete
  • Kill processes from running
    • C:Program FilesAzureStorageSyncAgentMAAgentMonAgent****.exe
  • Rename the Folder from
    • C:Program FilesAzure
    • C:Program FilesAzurev14
      • Note: If you get an „in use“ warning, the service still runs and/or its depend executables – See below „Services and executables blocking rename of C:Program FilesAzure“
      • (Used procexp.exe to search for this patch above and you will find all processes touching this folder)
  • Rename the Reg-Key from (Maybe the root cause)
    • ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftAzureStorageSyncAgentInstallOptions
    • ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftAzurev14StorageSyncAgentInstallOptions
      • Maybe the root cause: OsBuildInfo was still on Windows Server 2019  17763
      • Maybe root cause solution: Change to Windows Server 2022  20348

 After this procedure, you will not get an upgrade but an new endpoint in Azure File Sync.

Azure File Sync: Replacing Existing Server Endpoints – Microsoft Community Hub

So be sure, you check the health here and add the new endpoint to all Sync Groups necessary.

Services and executables blocking rename of C:Program FilesAzure

Maybe the root cause

Maybe the root cause solution

Eine Antwort schreiben

Ihre E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert

fünf × 2 =