Link to home
Start Free TrialLog in
Avatar of Edward Crist
Edward CristFlag for United States of America

asked on

Sysprep not running because of an Adobe package

Trying to run sysprep on a Windows 10 ENT 2019 LTSC image and keep getting this error

2019-07-25 08:13:06, Error                 SYSPRP Package AdobeNotificationClient_1.0.1.22_x86__enpm4xejd91yc was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

2019-07-25 08:13:06, Error                 SYSPRP Failed to remove apps for the current user: 0x80073cf2.

I believe if I uninstall or disable this, sysprep will run, but I'm not successful at doing either an uninstall or disable

I've uploaded my sysprep log files for reference.

Thanks!
setupact.log
setuperr.log
Avatar of ZeropointNRG
ZeropointNRG
Flag of Australia image

Login as local admin and delete all user profiles except admin and default.
Avatar of Edward Crist

ASKER

Nope...no joy. Removed all accounts as described, restarted and still getting the Adobe package error
How is that possible? Do you have the package on your system?
Yes, it's there.
Then remove it? Sorry, you tried that. Try to get the full package name

In PS. Get-AppxPackage -AllUser | Format-List -Property PackageFullName,PackageUserInformation
ASKER CERTIFIED SOLUTION
Avatar of ZeropointNRG
ZeropointNRG
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
If that doesn't work I'd probably redo setup and make sure nothing downloads in the background if you have internet.
Different app but I had a similar problem here, you can probably ue the same approach.

P
Thanks, guys....disconnecting from internet, I was able to remove the Adobe package and sysprep worked fine.

Always appreciative.
Avatar of Kevin Myers
Kevin Myers

@zeropointNRG Thank you for this answer man. This helped me out today with same issue. 👍

I know this is an old one but still relevant it seems :)

This doesn't work if the package was installed for some other user on the system and on windows 2016 the -AllUsers option isn't available on Appx module in powershell. Any other ideas?