App-V applications are unable to start and log error 0xc0000225 in Microsoft-AppV-Client\Debug log under the Log folder: Applications and ServicesLogs\Microsoft\AppV\ServiceLog.
Create the MaxAttachWaitTimeInMillisecond registry key that adds sleep delays to address timing issues when virtual environments are closed and quickly restarted but the underlying volume is not available for enumeration.
Use the credentials of a local admin to create and set the following registry key:
Registry subkey: HKLM\SOFTWARE\Microsoft\AppV\MAV\Configuration
Registry key name: MaxAttachWaitTimeInMilliseconds
Registry Type: DWORD
Set the value to a nonzero will enable the fix. The default is zero, the maximum value is 10,000 (without commas set in the registry)
A MaxAttachWaitTimeInMilliseconds value of 1 is often sufficient to eliminate application startup failures. If applications continue to fail with the same start error, use increasingly larger value to increase the amount of time the driver sleeps between enumeration checks. You may also review verbose events in the Microsoft-AppV-Client\Debug log under the Log folder: Applications and ServicesLogs\Microsoft\AppV\ServiceLog\ to see how much sleep was used/needed then readjust MaxAttachWaitTimeInMilliseconds accordingly.
Excessively large values for MaxAttachWaitTimeInMilliseconds may give the appearance of an application hang.
To use MaxAttachWaitTimeInMilliseconds, install a latest cumulative update (LCU) released March 19, 2019 or later, such as:
KB4489889 or higher LCU for Windows 10, version 1607 and Windows Server 2016.
KB4489888 or higher LCU for Windows 10, version 1703.
KB4489890 or higher LCU for Windows 10, version 1709.
KB4489894 or higher LCU for Windows 10, version 1803.
KB4482887 or higher LCU for Windows 10, version 1809 and Windows Server 2019.