locked
Crash caused by AppVStreamingUX.exe RRS feed

  • Question

  • Hi,

    I have a work computer that is crashing on startup with the error below. The computer is managed by my work. They would like to just reimage the machine but I don't want this - I just had it reimaged a couple of months ago and it is very disruptive. Can anyone help me?

    Faulting application name: AppVStreamingUX.exe, version: 0.0.0.0, time stamp: 0xd4690381
    Faulting module name: KERNELBASE.dll, version: 10.0.17763.1192, time stamp: 0x7889407f
    Exception code: 0xe0434352
    Fault offset: 0x0000000000039709
    Faulting process ID: 0x4500
    Faulting application start time: 0x01d64f322e712c69
    Faulting application path: C:\WINDOWS\system32\Appv\AppVStreamingUX.exe
    Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
    Report ID: aecfc3c5-41b8-4cbd-b1e3-aad7d0915d0d
    Faulting package full name:
    Faulting package-relative application ID:

    - System
    - Provider
    [ Name] Application Error
    - EventID 1000
    [ Qualifiers] 0
    Level 2
    Task 100
    Keywords 0x80000000000000
    - TimeCreated
    [ SystemTime] 2020-06-30T23:00:15.377776500Z
    EventRecordID 22211
    Channel Application
    Computer  [removed]
    Security
    - EventData
    AppVStreamingUX.exe
    0.0.0.0
    d4690381
    KERNELBASE.dll
    10.0.17763.1192
    7889407f
    e0434352
    0000000000039709
    4500
    01d64f322e712c69
    C:\WINDOWS\system32\Appv\AppVStreamingUX.exe
    C:\WINDOWS\System32\KERNELBASE.dll
    aecfc3c5-41b8-4cbd-b1e3-aad7d0915d0d

    Wednesday, July 1, 2020 11:16 PM

All replies

  • It seems AppVStreamingUX.exe is causing a CLR exception. There could be numerous issues causing this (missing core components/runtimes, corrupt packages/cache), but what is your main concern? Does this actually result in a GUI popup, or just an eventlog entry? I suppose this takes place after login and when the sync-appvpublishing scheduled task kicks in. You can disable the task, but you wont get any new/updates app-v packages from your backend (which you're already not getting because of this issue). 
    It's strange your IT (support) department doesn't want to look into this issue, but I don't know their service level agreements ;).

    Are currently published app-v packages working at all? Do you see any issues in the app-v eventlogs? I would first try to clear and clean-up all app-packages from delta-cache and packageroot. Also cleanup all leftovers in the registry. After that, perform the following powershell cmd: sync-appvpublishingserver 1.
    If this fails, have a look at the last package, which is possibly causing this issue.

    Roy Essers

    Thursday, July 16, 2020 2:18 PM