High After overwriting Picard files with the files in the 2.0-win64 download (because that's what it looked like I needed to do - let me know if that was wrong), I get this message when trying to start Picard: "Fatal Error: Failed to execute script tagger"
[PICARD-1221] Picard 2.0 won't start on Windows 10
My comment is about the recent beta. I could not update Affects Version as at the time I was writing my comment there was no such version in the list.
The application did not start until I removed the keys ca_providers and release_type_scores which contained sequences of @Variant(\0\0\0\x7f\0\0\0\xePyQt_PyObject\0\0\0\0\0). They did not cause issues for beta2.
Starting with a fresh copy from https://github.com/metabrainz/picard/releases/tag/2.0.0dev5 I had no problems to start Picard on a german Windows 10 Pro.
I also couldn't start dev5 without changing the .ini file. (I just deleted it - have a backup, of course.)
The following 3 entries in Picard.ini had values in the form like '@Variant(\0\0\0\x7f\0\0\0\xePyQt_PyObject\0\0\0\0\0)':
- release_type_scores
- ca_providers
- caa_image_types
After removing them I was able to start the application.
For me the version 2.0.0.dev4 started ok. 2.0.0.dev5 does not start with the mentioned error message.
I was able to replicate and fix this issue via config files from rdswift.
Yes, I tried that too. The only thing I didn't try was both at once, but I guess I could.
Fixed in latest daily build.