Sysprep warning message in 8.5.2

[donho]

SYSPRP Package NotepadPlusPlus_1.0.0.0_neutral__7njy0v32s6xk6 was installed for a user, but not provisioned for all users.
https://community.notepad-plus-plus.org/topic/24345/notepad-v8-5-2-release/19?_=1681357704510

Not sure if it’s NppShell issue though.
What do you think @GurliGebis ?

[GurliGebis]

It is the same as when we try to install it for all users.
Sysprep complains that the package isn't installed for all users - so when the image they make is installed, the new user will not be have the package installed.

However, the multi-user fix we did earlier this week also works there. So the first time they right click a file after they create the user, it will be there.

This requires 8.5.3 though, so the version they are using (8.5.2) doesn't do that 🙂

[donho]

@GurliGebis

This requires 8.5.3 though, so the version they are using (8.5.2) doesn't do that

Sorry I don't follow you - what's in v8.5.3 makes difference?

It is the same as when we try to install it for all users.
Sysprep complains that the package isn't installed for all users - so when the image they make is installed, the new user will not be have the package installed.

So if I understand correctly, while installer registering NppShell.dll for the Adm user, Sysprep has detected it and complains? If it is, Sysprep will always complain with our current solution (installing for user on the first use), won't it?

[GurliGebis]

@donho in the test builds we have now, this code exists:

nppShell/Installer.cpp

Line 409 in e250ff9

thread ensureRegistrationThread = thread(EnsureRegistrationOnCurrentUserWorker);

Sysprep complains that the package is only installed for a normal user, and not provisioned for everyone (which is what you cannot do for a sparse package - or to be more specific, you can do it, but it doesn't get installed for other users when they log in).
So since the code I link above exists, they should just ignore the warning from sysprep, since we handle registering the package for new users at the first right click on a file.

[donho]

@GurliGebis

So since the code I link above exists, they should just ignore the warning from sysprep, since we handle registering the package for new users at the first right click on a file.

So TEST20 should fix it, shouldn't it?

[GurliGebis]

@donho it will make sure it is installed for the user on first right click.
It won't prevent sysprep from showing that warning, since it will complain about it, but the warning can be safely ignore, since it is working as intended

[donho]

@GurliGebis

it will make sure it is installed for the user on first right click.

You mean on the 2nd right click, right?

It won't prevent sysprep from showing that warning, since it will complain about it, but the warning can be safely ignore, since it is working as intended

OK, thank you for your answer.

[GurliGebis]

@donho on the first right click, it will trigger the install of the msix package, so it will be there on the second right click 🙂

[donho]

@GurliGebis

@donho on the first right click, it will trigger the install of the msix package, so it will be there on the second right click 🙂

Yes, sure. Sorry for misreading. Thank you for the reply.

[GurliGebis]

🙂

[Hammerfest]

Thanks everyone for reporting this error, I was just building new images for family systems updating to 11 and kept running into this error when trying to sysprep generalize when it worked without issue a few months ago!

Looks like it will be resolved in 8.5.3 so I will keep an eye out and test when it drops!

EDIT: if TEST20 is supposed to resolve the issue, it does not, this PREVENTS sysprep generalize from completing.

[GurliGebis]

@Hammerfest sysprep fails if a package is provisioned for the user but not the system?

[Hammerfest]

Correct, exact message at the opening comment

2023-04-22 15:45:17, Error                 SYSPRP Package NotepadPlusPlus_1.0.0.0_neutral__7njy0v32s6xk6 was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.
2023-04-22 15:45:17, Error                 SYSPRP Failed to remove apps for the current user: 0x80073cf2.
2023-04-22 15:45:17, Error                 SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.
2023-04-22 15:45:17, Error                 SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2
2023-04-22 15:45:17, Error                 SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2
2023-04-22 15:45:17, Error                 SYSPRP RunPlatformActions:Failed while validating Sysprep session actions; dwRet = 0x3cf2
2023-04-22 15:45:17, Error      [0x0f0070] SYSPRP RunDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2
2023-04-22 15:45:17, Error      [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2

[GurliGebis]

@Hammerfest can you try this, and then run sysprep again:
Get-AppxPackage -Name *NotepadPlusPlus* | Remove-AppxPackage

[GurliGebis]

The package will be reinstalled automatically

[Hammerfest]

This worked, it should be noted however that if you create a template user (not done often by many) it will need to be done on both the user and sysprep account or it will still fail.

Might be to much of a PITA to properly resolve this to simply install upon account creation or provide an integration pack like Microsoft does for some of its tools.