App-V Chrome 75 - Unable to start correctly

[robyholmes]

Hi All,

I'm trying to update our Chrome package in App-V 5.1 but each time I do, I get the following error:

The application was unable to start correctly (0xc0000142). Click OK to close the application.

 

In event viewer I see the following error in the App-V Virtual Applications log:

Error 18005

The virtual application 'C:\....chrome.exe' could not be started because the App-V Subsystem 'Virtual Filesystem' could not be initialized. {error: 0x74300E0A-0x20006}

 

I've looked up this error and it seems to reference NtfsDisable8dot3NameCreation needing to be enabled (Set to 2):

https://support.microsoft.com/en-gb/help/2777003/an-app-v-v5-virtualized-application-fails-to-start-with-error-0xc00001

However our clients already have this enabled and so does the sequencing machine.

 

I've re-packaged it again this time using the enterprise installer rather than offline standalone installer but I'm getting the same error. Other packages and my older Chrome package are running fine.

 

Has anyone managed to package up the latest Chrome or come across this problem before? I'm not sure what to try next.

 

Thanks, Rob

[robyholmes]

I've managed to resolve this. I inspected the package using the package editor and found some Windows & Microsoft folders in the package which didn't reference anything to do with Chrome. Remove them and re-published the package and it appears to be working.

[lbj]

I'm having the exact same issue. Can you confirm what version of the Sequencer you were using? We are using Win 1809 sequencer and I have not been able to resolve. Any assistance you can provide would be helpful.

[robyholmes]

I'm having the exact same issue. Can you confirm what version of the Sequencer you were using? We are using Win 1809 sequencer and I have not been able to resolve. Any assistance you can provide would be helpful.

 

I'll need to get back to on your on Sequencer but I found you needed to remove a lot of 'Windows' files & folders, plus any registry items for Windows or other services other than Chrome.

 

However, I then found it wouldn't allow users to choose Chrome as the default browser so I went back to deploying by MSI. As that method worked and the only advantage to App-V for Chrome is it would save space it someone didn't open it, but everyone does.