Hello Johannes,
That was happening because of some noise registry entries captured during the repackaging session.
I will paste below the reply from email:
I've finished my investigations regarding this and here would be the conclusions:
- the keys from under SYSTEM\WaaS\WaaSMedic\TaskStore are system keys, not really related to your setup package. Most likely, during the repackaging process, some system process modified those entries and thus the repackager captured them.
By default, you can find these keys on a clean machine. If you try to modify them, you will see that they can't be modified, even if you are an administrator.
Additionally, when doing a before and after installation comparation of these keys, you can notice that they are not actually modified.
With that being said, we can consider these keys as "noise" and remove them from the project.
- regarding the DRIVERS\DriverDatabase\DriverPackages\amyuni.inf_amd64_59192b45a3f57cbb key, this probably happens because we are not actually installing amyuni.inf as a driver.
To avoid this, please go to "Drivers" page and add the .INF file there, so it can be installed as a driver.
- besides those two, some other error will occur for HKEY_LOCAL_MACHINE\Microsoft\IdentityCRL\NegativeCache key. This is similar to the first.
What I can suggest here would be to do the repackaging process in a Sandbox environment as that is even "cleaner" than the VMs - we have added this support not so long ago.
Hope this helps!
Best regards,
Catalin