[Azure] Installing windows feature on Windows Server 2025 takes longer time

Question

[Azure] Installing windows feature on Windows Server 2025 takes longer time

Rushikesh Gaidhani 166

Hello,

I am trying to install Windows features on a Azure VM with a Windows 2025 Datacenter Azure marketplace image. The install of the feature takes longer time than compare to the previous Windows 2022 Datacenter Azure marketplace image (Please note that I've not made any modifications to the image).

Has there been a change in the new Windows 2025 Datacenter Azure image that could be causing this delay?

User's image

Vamsi Ram Annepu 915 Reputation points Moderator

2025-04-29T01:18:13.84+00:00

Hi Rushikesh Gaidhani,
As Windows 2025 Datacenter Azure marketplace image has high size, newer version and due to some internet connectivity issue the installation of the feature might have taken longer time than compared to the previous Windows 2022 Datacenter Azure marketplace image.
To verify this you can also check "Activity Logs" and "Windows Update Logs".

Feel free to reach out if you have any further queries.
If you found the information useful, please click "Upvote" on the post to let us know.
Rushikesh Gaidhani 166 Reputation points

2025-04-29T02:25:39.0066667+00:00

Hello Vamsi Ram Annepu, I hit the same issue every time I try to install a feature on multiple instances with 2025 image. I don't think it is some internet connectivity issue.
Mounika Reddy Anumandla 7,135 Reputation points Moderator

2025-04-30T05:12:48.7466667+00:00

Hi Rushikesh Gaidhani,

Similar issue is reported here https://github.com/PowerShell/PowerShell/issues/24500 and one user confirmed that he could solve the problem by using this PowerShell command as administrator, it will take a while again: Remove-WindowsFeature -Name WindowsAdminCenterSetup

This will remove the Windows Admin Center setup, which is not required on most systems. After removal, the Get-WindowsFeature works normally again!

Hope this helps!

Let me know if you have any further queries!
Rushikesh Gaidhani 166 Reputation points

2025-04-30T14:47:09.89+00:00

Hello Mounika Reddy Anumandla, Removing the AdminCenterSetup still doesn't help, it still takes the same amount of time.
Vamsi Ram Annepu 915 Reputation points Moderator

2025-05-03T12:51:12.23+00:00

Hi Rushikesh Gaidhani,
Could you share the RAM, Hard drive space of the VM, logical processors on the device (CTRL+SHIFT+ESC > Performance tab > number of logical processors).
Wagner Silva 80 Reputation points Microsoft Employee

2025-05-03T13:50:31.41+00:00
The error 0x80073701 (ERROR_SXS_ASSEMBLY_MISSING) indicates that a referenced assembly is missing, commonly due to corrupted or incomplete system components. This often happens when installing features like IIS on Windows Server in Azure.

Recommended Troubleshooting Steps:

1. Run System File Checker and DISM

Open Command Prompt as Administrator and run the following:

sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth

DISM /Online /Cleanup-Image /StartComponentCleanup

DISM /Online /Cleanup-Image /ScanHealth

These commands will scan for and fix corrupted system files.

2. Check for Pending Updates

Run:

dism /online /get-packages /format:table | findstr Pending

If there are pending updates, restart the server.

If issues persist, you can rename C:\Windows\WinSxS\Pending.xml to Pending.xml.old and restart.

3. Review CBS.log for Details

Examine the log at C:\Windows\Logs\CBS\CBS.log for related error entries like:

ERROR_SXS_ASSEMBLY_MISSING

Failed to pin deployment

Identify the missing KB or package and manually install it using:

DISM /Online /Add-Package /PackagePath:C:\Path\To\KBxxxxxx.cab

4. Check Language Packs

Make sure the system language matches the installed language packs. Mismatches can cause feature installation issues.

5. In-place Upgrade (if needed)

As a last resort, perform an in-place upgrade by:

Mounting the correct Windows Server ISO

Running setup.exe

Choosing the option to keep files and applications This can repair the system without data loss.

6. Run Windows Update Troubleshooter

Go to:

Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update

Run the troubleshooter to fix update-related problems.

If the issue persists, consider deploying a new Azure VM with the required features and migrating workloads if feasible.
Wagner Silva 80 Reputation points Microsoft Employee

2025-05-03T14:15:11.1333333+00:00

Hi,

1. Repair the System Image with DISM

Open Command Prompt as administrator and run the following commands:

dism /online /cleanup-image /scanhealth

dism /online /cleanup-image /restorehealth

These commands check and fix the integrity of system files. After completion, restart the server and try to install the feature again.

2. Run the System File Checker (SFC)

Open Command Prompt as administrator and run:

sfc /scannow

This command checks and repairs corrupted system files. After completion, restart the server and try to install the feature again.

3. Check and Fix Language Packs

If the server was installed with an incorrect language pack or if there are additional installed language packs, this may cause issues with installing features. Run the following command to check and remove unwanted language packs:

lpksetup /u <Package_ID>

Replace <Package_ID> with the identifier of the language pack you want to remove. After removal, restart the server and try to install the feature again.

4. Install Pending Updates

Check for pending updates in Windows Update and install them. Some updates may fix issues related to feature installation. After installing updates, restart the server and try installing the feature again.

5. Perform a Repair Installation

If the above solutions don’t resolve the issue, consider performing a repair installation of Windows Server. To do this, mount the Windows Server 2019 installation media with the correct language pack and run setup.exe as administrator. Choose the option to keep existing files and applications. This operation reinstalls the operating system without affecting existing data.

f the problem persists after trying these solutions, it is recommended to contact Microsoft support for further assistance.

1 answer

Your answer

Vamsi Ram Annepu 915 Reputation points Moderator

2025-04-29T01:18:13.84+00:00

Hi Rushikesh Gaidhani,
As Windows 2025 Datacenter Azure marketplace image has high size, newer version and due to some internet connectivity issue the installation of the feature might have taken longer time than compared to the previous Windows 2022 Datacenter Azure marketplace image.
To verify this you can also check "Activity Logs" and "Windows Update Logs".

Feel free to reach out if you have any further queries.
If you found the information useful, please click "Upvote" on the post to let us know.
Rushikesh Gaidhani 166 Reputation points

2025-04-29T02:25:39.0066667+00:00

Hello Vamsi Ram Annepu, I hit the same issue every time I try to install a feature on multiple instances with 2025 image. I don't think it is some internet connectivity issue.
Mounika Reddy Anumandla 7,135 Reputation points Moderator

2025-04-30T05:12:48.7466667+00:00

Hi Rushikesh Gaidhani,

Similar issue is reported here https://github.com/PowerShell/PowerShell/issues/24500 and one user confirmed that he could solve the problem by using this PowerShell command as administrator, it will take a while again: Remove-WindowsFeature -Name WindowsAdminCenterSetup

This will remove the Windows Admin Center setup, which is not required on most systems. After removal, the Get-WindowsFeature works normally again!

Hope this helps!

Let me know if you have any further queries!
Rushikesh Gaidhani 166 Reputation points

2025-04-30T14:47:09.89+00:00

Hello Mounika Reddy Anumandla, Removing the AdminCenterSetup still doesn't help, it still takes the same amount of time.
Vamsi Ram Annepu 915 Reputation points Moderator

2025-05-03T12:51:12.23+00:00

Hi Rushikesh Gaidhani,
Could you share the RAM, Hard drive space of the VM, logical processors on the device (CTRL+SHIFT+ESC > Performance tab > number of logical processors).
Wagner Silva 80 Reputation points Microsoft Employee

2025-05-03T13:50:31.41+00:00

The error 0x80073701 (ERROR_SXS_ASSEMBLY_MISSING) indicates that a referenced assembly is missing, commonly due to corrupted or incomplete system components. This often happens when installing features like IIS on Windows Server in Azure.

Recommended Troubleshooting Steps:

1. Run System File Checker and DISM

Open Command Prompt as Administrator and run the following:

sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth

DISM /Online /Cleanup-Image /StartComponentCleanup

DISM /Online /Cleanup-Image /ScanHealth

These commands will scan for and fix corrupted system files.

2. Check for Pending Updates

Run:

dism /online /get-packages /format:table | findstr Pending

If there are pending updates, restart the server.

If issues persist, you can rename C:\Windows\WinSxS\Pending.xml to Pending.xml.old and restart.

3. Review CBS.log for Details

Examine the log at C:\Windows\Logs\CBS\CBS.log for related error entries like:

ERROR_SXS_ASSEMBLY_MISSING

Failed to pin deployment

Identify the missing KB or package and manually install it using:

DISM /Online /Add-Package /PackagePath:C:\Path\To\KBxxxxxx.cab

4. Check Language Packs

Make sure the system language matches the installed language packs. Mismatches can cause feature installation issues.

5. In-place Upgrade (if needed)

As a last resort, perform an in-place upgrade by:

Mounting the correct Windows Server ISO

Running setup.exe

Choosing the option to keep files and applications This can repair the system without data loss.

6. Run Windows Update Troubleshooter

Go to:

Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update

Run the troubleshooter to fix update-related problems.

If the issue persists, consider deploying a new Azure VM with the required features and migrating workloads if feasible.
Wagner Silva 80 Reputation points Microsoft Employee

2025-05-03T14:15:11.1333333+00:00

Hi,

1. Repair the System Image with DISM

Open Command Prompt as administrator and run the following commands:

dism /online /cleanup-image /scanhealth

dism /online /cleanup-image /restorehealth

These commands check and fix the integrity of system files. After completion, restart the server and try to install the feature again.

2. Run the System File Checker (SFC)

Open Command Prompt as administrator and run:

sfc /scannow

This command checks and repairs corrupted system files. After completion, restart the server and try to install the feature again.

3. Check and Fix Language Packs

If the server was installed with an incorrect language pack or if there are additional installed language packs, this may cause issues with installing features. Run the following command to check and remove unwanted language packs:

lpksetup /u <Package_ID>

Replace <Package_ID> with the identifier of the language pack you want to remove. After removal, restart the server and try to install the feature again.

4. Install Pending Updates

Check for pending updates in Windows Update and install them. Some updates may fix issues related to feature installation. After installing updates, restart the server and try installing the feature again.

5. Perform a Repair Installation

If the above solutions don’t resolve the issue, consider performing a repair installation of Windows Server. To do this, mount the Windows Server 2019 installation media with the correct language pack and run setup.exe as administrator. Choose the option to keep existing files and applications. This operation reinstalls the operating system without affecting existing data.

f the problem persists after trying these solutions, it is recommended to contact Microsoft support for further assistance.

Answer 1

Alex Burlachenko 25,120 MVP Volunteer Moderator

Dear Rushikesh Gaidhani,

thank you for your question regarding the installation time differences between Windows Server 2022 and 2025 on Azure VMs. While Microsoft has not officially documented specific changes in Windows Server 2025 that would directly cause slower feature installations, the increased duration (1 minute 43 seconds vs. 15 seconds) could be attributed to Enhanced Security Scans Windows Server 2025 may perform more thorough validation of feature components before installation.

Updated Dependencies Features like File-Services might have expanded dependencies in newer OS versions.

Azure Image Optimizations The 2025 Azure Edition could include additional telemetry or background processes during setup.

For deeper investigation, you can par example

Compare installation logs (Get-WindowsFeature -LogPath <path>) between versions.

Check for known issues in the Windows Server 2025 Release Notes.

Monitor real-time resource usage during installation using PerfMon or Azure VM Metrics.

If this is impacting workflows, consider scripting the installation with -Restart (if acceptable) to automate the post-install reboot.

Best regards,
Alex
P.S. If my answer help to you, please Accept my answer
PPS That is my Answer and not a Comment

Anonymous

2025-05-07T06:34:30.2333333+00:00

Hi @Rushikesh Gaidhani

Thank you, Alex great explanation, just to add a couple of things. Like it is more important to check if the azure vm guest agent is up to date or not sometimes an older agent can cause the delays during the setup or installations.

You can check using the below powershell command:

Get-Item "C:\WindowsAzure\Packages\WaAppAgent.exe" | Select-Object -ExpandProperty VersionInfo

Then check it to the latest available version from microsoft < https://learn.microsoft.com/en-us/azure/virtual-machines/extensions/agent-windows#agent-versions >

you could also try installing the feature using a local source path like D:\Sources\SxS instead of relying on updates. it might help to reduce the time.

Like instead of running this Install-WindowsFeature Net-Framework-Core

You can do Install-WindowsFeature Net-Framework-Core -Source D:\Sources\SxS

D:\Sources\SxS < it comes from windows server ISO or mounted installation media. the SxS(side by side) it will contain the necessary binaries and assemblies.

you can mount the ISO in azure vm using portal or upload the SxS folder to a data disk or file share.

Please let us know if this was helpful. If it was, feel free to upvote it to assist others in the community as well.
Anonymous

2025-05-08T04:56:12.85+00:00

Hi @Rushikesh Gaidhani

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, please respond with more details and we will try to help.
Anonymous

2025-05-09T07:28:40.85+00:00

Hi @Rushikesh Gaidhani

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, please respond with more details and we will try to help.

Martin Horvath 0

This is still an issue for us when we setup new VMs. If we compare the following azure provided images:

publisher	offer	sku
MicrosoftWindowsServer	WindowsServer	2025-Datacenter
MicrosoftWindowsServer	WindowsServer	2022-Datacenter
MicrosoftWindowsServer	WindowsServer	2019-Datacenter

We can see that Windows Server 2025 takes a considerable amount of time longer to do simple DISM feature queries as well as using the powershell command Install-WindowsFeature X.

This isn't a major issue if you are installing a single VM. However if you deploy more complex setups where you have dependencies between different VMs it quickly adds up.

This is the clearest OS-bound difference. All values are seconds. The win2025 values repeat in all three runs.


Operation	2k19	2k22	2k25 (3 runs)
First DISM feature query, boot run (File-Services, up to date)	14	17	200 / 210 / 211
First DISM feature query, main run (File-Services, up to date)	14	19	192 / 209 / 214
DISM install: TelnetClient	18	17	106 / 118 / 117
DISM install: IIS-ApplicationInit	28	21	112 / 128 / 128
Install-WindowsFeature check: storage-services	49	16	152 / 166 / 166
Install-WindowsFeature checks: fs-fileserver, powershell, wow64	49 each	5-7 each	6-7 each
Total time in feature operations per deploy	330	111	791 / 865 / 862

win2025: every cold servicing operation costs 94-166 s: the first DISM query of each chef run, each real DISM install, and the first ServerManager call. Cached re-checks are free. This is a deterministic ~9-10 min tax per deploy.

win2019: DISM is fast, but each ServerManager (Install-WindowsFeature) check costs ~49 s.

win2022: all paths are near-instant.