Microsoft 365 Personal installation fails on Windows Server 2025 with AppV error

Hi Ss Aa,

How is your issue going? Has it been resolved yet? If it has, please consider accepting the answer as it helps others sharing the same problem benefit too. Thank you :)

VP

Hi Ss Aa,

Standard Windows performance counters typically cap total CPU utilization at 100 percent, though some monitoring tools aggregate individual core usage. On a server with 6 vCPUs, the maximum possible aggregated value is 600 percent, meaning your recorded spike of 945 percent is mathematically impossible for actual physical usage. This artificially inflated reading is a known calculation error in virtualized environments rather than a genuine resource exhaustion event. When a virtual machine experiences a momentary pause, commonly known as a VM stun, the guest operating system's internal clock temporarily falls out of sync with the hypervisor. This typically happens during VMware snapshot creation, snapshot consolidation, or vMotion migrations. Upon resuming, the performance counter calculates active processing time against a distorted, unnaturally short elapsed time period, producing a severe mathematical spike. The absence of ESXi or vCenter alarms confirms this is an internal guest calculation anomaly. You can verify this behavior by cross-referencing your vCenter task history or backup software logs around the exact timestamp of the spike to identify any automated snapshot operations.

To identify resource-heavy applications using the native Windows Performance Monitor, you will need to configure a custom data collection schedule. Open the Run dialog, execute perfmon to launch the tool, navigate to the Data Collector Sets section, and create a new User Defined set. You must manually add a performance counter data collector and select the Percent Processor Time counter under the Process category, ensuring you choose all instances to capture every running application. This configuration tracks the thread execution time for individual processes, allowing you to see exactly which application is demanding resources. After saving and starting this collection to run in the background, the tool will generate a log file typically stored in the PerfLogs directory on your system drive. Opening this log file directly within Performance Monitor allows you to click on the highest peaks in the generated graph, which will immediately highlight the corresponding process at the bottom of the screen to identify the responsible application.

Hope this answer brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.

VP

Microsoft 365 Personal cannot be used as a supported, locally installed Office client on Windows Server 2025, and switching to a Microsoft 365 Apps for business SKU does not change that.

From the compatibility and lifecycle information:

• Microsoft 365 Apps is supported on Windows Server 2025 while the OS is in Mainstream Support.
• However, Microsoft 365 Apps is only supported on Windows Server with Desktop Experience, and only in the enterprise/organization scenarios described (for example, in the “Microsoft server applications compatibility for Windows Server” table and the migration guidance).
• The guidance for organizations currently hosting Microsoft 365 Apps on Windows Server is to move to client hosting solutions such as Windows 365 or Azure Virtual Desktop, not to install Microsoft 365 consumer subscriptions directly on the server.

The App-V–related error on Windows Server 2025 when trying to install Microsoft 365 Personal via ODT is a symptom of this unsupported scenario rather than something that can be fixed with a configuration tweak. The context provided does not document any supported workaround for installing a Microsoft 365 Personal (home) subscription on Windows Server 2025, nor any supported method to make App-V–based components work there for this use case.

Regarding a refund for the subscription amount (859.99 SAR), refund and billing handling is not covered in the provided material. The documented guidance is limited to technical supportability and migration options; it does not include licensing or refund processes.

For a supported lab setup with Microsoft 365 Apps on server-class infrastructure, the documented direction is to use:

• Windows 365 cloud PCs, or
• Azure Virtual Desktop

and run Microsoft 365 Apps there, instead of installing a Microsoft 365 Personal subscription directly on Windows Server 2025.

References:

• Microsoft 365 Apps migration from Windows Server
• Microsoft server applications compatibility for Windows Server (windows-server-2025)
• Windows Server end of support and Microsoft 365 Apps