locked
Cannot Start AppVMon Service error in Windows 10 1803 RRS feed

  • Question

  • I've created a VM running Windows 10 1803, installed the App-V Sequencer from the ADK for 1803 but when I try to sequence an application I get an error saying that the AppVMon service can't be started.

    I also get Event IDs 200 and 5002 in the Event Log but can't find any useful information about how to resolve this problem.

    I'm not using Secure Boot on the VM, which seems to be a common issue.

    Anyone else got any thoughts on what's wrong?

    Cheers for now

    Russell

    Friday, June 29, 2018 9:42 AM

Answers

  • Good call......my mistake, I had a problem on the App-V Server and the Windows 10 client!

    The KB was installed on the Management/Database server to resolve a problem with Publishing an Appv file.

    The problem with the Windows 10 client was resolved by the "2018-06 Cumulative Update for Windows 10 Version 2803 (KB4284848).

    Sorry about that.

    Russell  
    • Marked as answer by RSBurnell Monday, July 2, 2018 6:23 PM
    Monday, July 2, 2018 6:23 PM

All replies

  • is this 100% reproducible? 
    Monday, July 2, 2018 4:13 PM
  • After more investigation I found a KB article (listed below) that included a hotfix that I applied and that resolved the problem:

    https://support.microsoft.com/en-us/help/3168628/september-2016-servicing-release-for-microsoft-desktop-optimization-pa

    Cheers for now

    Russell

    • Marked as answer by RSBurnell Monday, July 2, 2018 5:12 PM
    • Unmarked as answer by RSBurnell Monday, July 2, 2018 6:23 PM
    Monday, July 2, 2018 5:12 PM
  • that doesn't make sense to me, the link you mentioned is a hotfix patch for appV 5.1, how can you use that on Windows 10 1803 machine?
    Monday, July 2, 2018 5:49 PM
  • Good call......my mistake, I had a problem on the App-V Server and the Windows 10 client!

    The KB was installed on the Management/Database server to resolve a problem with Publishing an Appv file.

    The problem with the Windows 10 client was resolved by the "2018-06 Cumulative Update for Windows 10 Version 2803 (KB4284848).

    Sorry about that.

    Russell  
    • Marked as answer by RSBurnell Monday, July 2, 2018 6:23 PM
    Monday, July 2, 2018 6:23 PM