Autodesk launch issue

[HallJ0816]

Has anyone encounter this issue where when you first initially launch Autodesk package on a non-persistent desktop. Autodesk triggers a windows installer prompt which ends up getting "Error 1321. The installer has insuffficient privileges to modify this file: C:\Windows\Installer\{233948r-4444-6666-5445-5959t5t5t5}\Aoem162_icon.exe".  If I click ignore through those 1321 errors the splash screen for the product eventually comes up and program works fine but I cant figure out how to get around that first launch issue Im using - AppVol 2.18 - DEM 9.10 - Horizon 7.10 - Non-Persistent Instant Clone Pools

[cliffvmwareeuc]

Do you see anything of interest in the App Volumes svservice.log, Horizon Agent debug log or Windows Events on the VM at the time of the message appearing?

[HallJ0816]

@cliffvmwareeuc There's nothing in either Horizon or AppVolume (svservice) logs that report any type of errors Windows Event viewer just show the 1321 errors during the application launch - The verbiage from event viewer is pasted below Event ID 11321 Product: Autodesk AutoCAD Map 3D 2018 - English -- Error 1321. The Installer has insufficient privileges to modify this file: C:\Windows\Installer\{28B89EEF-1002-0409-2102-CF3F3A09B77D}\TBClient.ico. Product: Autodesk AutoCAD Map 3D 2018 - English -- Error 1321. The Installer has insufficient privileges to modify this file: C:\Windows\Installer\{28B89EEF-1002-0409-2102-CF3F3A09B77D}\AcadDWGAssoc.ico.

[cliffvmwareeuc]

There can be issues with Autodesk and AutoCad as well as other similar applications because they are so large and require time to place their registry keys and settings as well as other services.

For testing purposes, if the application is installed in an appstack you could try disabling the reverse_replicate registry setting in the HKLM\SYSTEM\CurrentControlSet\services\svdriver\Parameters registry location on the base image (Will increase logon time)

Or

Create a writable volume for a test user and see if that resolves it at there may be some module that needs to write to a location that may not be present or already populated.

If the application is installed on the base image then without appstacks assigned at all does it work ok?

I would also recommend while testing or before testing that you open a case to help you with this.