Default App

[rfriedrich]

Hello, installed the newest update on a PC w/o any previous versions, installed silent. With parameter set that PDF-Xchange will be default. Did not work, was not the standard app. When I tried the previous version, with the same flag all went well.

Is there a bug/change?

Thanks in advance.

cu
F.

[Daniel - PDF-XChange]

Hello, rfriedrich

Thank you for the post, I have not seen any other reports along these lines yet with 396, and in testing, it does seem to properly assign the Default application on this end. Perhaps there was a conflict, or windows did not respond to the request for default status for some other reason (It is wont to do that occasionally).

If this is a single device scenario, you can follow the steps here to set the Editor as your default app manually: https://www.pdf-xchange.com/knowledgeba ... PDF-Viewer

If this is a case of a larger organization or deployment, you can find options to change the default apps here: https://help.pdf-xchange.com/sysadmin/m ... ault2.html

Kind regards,

[rfriedrich]

Hello, tried it again, clean windows, w/o PDFXChange previously installed, with Parameter SET_AS_DEFAULT=1 and it did not register properly.

cu
F.

[Daniel - PDF-XChange]

Hello, rfriedrich

Thank you for trying that, In this case, an installation log would be helpful, as I believe it should indicate if the set as default action was properly attempted and what the result was.

You will find the logs contained in this folder:
%tmp%
and will be named as "MSIxxxx.log" (Where the x's are random alphanumeric characters)

Assuming our software was the last installer you ran, you can upload the most recent one to our upload server, here:
https://files.pdf-xchange.com/s/xdyoWBscqCWFGR9

Please let me know when the upload is completed, so I can bring it to the dev team for further inspection.

Kind regards,

[rfriedrich]

Hello, thanks! Uploaded the log with the lateste version and the version before. Latest fails, the other succeds tested in a clean VM W24H2 X64 German.

Hope You can resolve it, I am wondering that this works because setting standard apps is not so easy nowadays w/o using the GUI.

cu
F.

[Daniel - PDF-XChange]

Hello, rfriedrich

And thank you for sending those along, I see them, and have passed them up to the Dev team for review. I will let you know as soon as I hear back from them on that investigation.

Kind regards,

[Daniel - PDF-XChange]

Hello again!

From what we can see, the request to set defaults was pushed through as expected. We did make some changes here, specifically, adding a new secondary method to try and change defaults, which should only have expanded the viable scenarios in which this happens, not reduced it....

The team is first asking if you can confirm, on the device where this is not working, are you also running win11 24H2, or is that device on a different version/build of windows?
Secondly, They are wondering if you have tested, can the app default be set properly using the Editor UI after installation? This option is located in the preferences menu (Ctrl_K) under the File associations category. Please try changing the "default app for PDF files" to "make default" then click apply (IT WILL revert to saying do not change, this is expected). Then close the Editor, and see if the change had an effect?

Kind regards,

[rfriedrich]

Hello, yes both are 24H2. On the first system (I reset it every day when I used it and install the app every day I use the PC) I have now the work around to start the app after installing. The app asks for change, I use then "Yes, for this user" and everything runs smoothly.

It seems that only when the installer wants to change: it fails. In the UI all is fine. This occured only with your newest build. I use the app for a long time and had never this problem.

I know that MS works to prevent programmatically changes but it wonders why your two build acts differently on the same build of W11.

Thanks for Your support, like your app for so long, because it works so flawless.

cu
F.

[Daniel - PDF-XChange]

Hello, rfriedrich

I apologize for the delay here, we have been quite busy of late. Ivan should hopefully be getting back to us on this shortly, but I wanted to let you know we have not forgotten this case.

Kind regards,