Automated File Associations setup

garlin said:
Colpa mia. L'ultima riga dovrebbe leggere " cmd.exe /c " e non " cmd.exe /s ", altrimenti CMD non esce.
garlin said:
Colpa mia. L'ultima riga dovrebbe leggere " cmd.exe /c " e non " cmd.exe /s ", altrimenti CMD non esce.

Puoi aggiungere altri FTA se ne hai bisogno. Per esempio:
[CODICE]
.pdf, AcroExch.Document.DC
[/CODICE]
Click to expand...
Click to expand...



garlin said:
Puoi aggiungere altri FTA se ne hai bisogno. Per esempio:
[CODICE]
.pdf, AcroExch.Document.DC
[/CODICE]
Click to expand...

garlin said:
My bad. The last line should read "cmd.exe /c" not "cmd.exe /s", otherwise CMD doesn't exit.

You can append more FTA's if you need them. For example:
Code: 
.pdf, AcroExch.Document.DC
Click to expand...
Hi, I'll make the changes you just suggested, thank you very much, so it should be cmd.exe /c rmdir /s /q C:\SetUserFTA , right? I had also already tried to append to:

http, ChromeHTML

https, ChromeHTML

.htm, ChromeHTML

.html, ChromeHTML

.pdf, AcroExch.Document.DC but it doesn't work, the pdf browser remains Edge.
 
So the config.txt file should look like this:

.http, ChromeHTML
.https, ChromeHTML
.htm, ChromeHTML
.html, ChromeHTML
.pdf=AcroExch.Document.DC
.pdfxml=AcroExch.pdfxml
Exact?
 
If this is not the case, could you post me a single config.txt file that contains the instructions for associating the PDFs with Acrobat Reader and the HTML and HTM files with Google Chrome? I know maybe I'm asking a lot but I would be grateful
 
My point is if you install Adobe Reader in Post-Setup, the installer forces the PDF association without having to use SetUserFTA. You only have to use SetUserFTA if the app's installer doesn't do it the right way.
 
As soon as I install Acrobat Reader, with post-setup, the PDF files are displayed with Edge and not with Acrobat Reader. With chrome, also installed with post-setup instead by setting the config.txt file as below:
.http, ChromeHTML
.https, ChromeHTML
.htm, ChromeHTML
.html, ChromeHTML

it works, chrome becomes the default browser, so I expected that what worked with chrome would also work with acrobat reader, instead also by setting the config.txt file as follows:
.http, ChromeHTML
.https, ChromeHTML
.htm, ChromeHTML
.html, ChromeHTML
.pdf=AcroExch.Document.DC
.pdfxml=AcroExch.pdfxml

PDFs don't open with default reader.
 
Exactly, that was the mistake!! Furthermore, in a first attempt I had forgotten to put the comma after .pdf, then I looked closer and noticed the error, since Chrome was the default browser with the comma so I also put the comma for pdfs. Thanks a lot anyway! Very kind!!
 
I have used setuserfta since 2022 to change the standard browser. Today I realized that for HTTP and HTTPS it doesn't work anymore, it always stays the same. For FTP it still works. I wonder why. Do you encounter the same problem? So, actually at the moment I can't change my standard browser anymore using this tool. I hate these Microsoft iditos!
 
I haven't seen SetUserFTA fail when it's correctly called. The last update for any File Type Association will always win, so make sure it's not another Windows process working in the background.

To check your work, add a second line in Post-Setup:
Code: 
SetUserFTA [your command]
SetUserFTA get > C:\filetypes.txt

The log file will confirm if HTTP & HTTPS were correctly changed at the time. If it changes afterwards, you need to check if Edge updater is running to restore Edge as the primary browser.
 
Actually on my systems (Windows 10 and 11) it doesn't work anymore. And the author of SetUserFTA confirmed this to me in an e-mail. Microsoft did some changes which block the change of HTTP and HTTPS as well as PDF associations via this app. There will be a fix but it seems to need admin rights and a reboot, so the good thing of not having to use the tool with admin rights or a special interaction is gone and for me the tool is useless unfortunately.
 
It works for me, it sets Chrome as my default web page viewer, and Acrobat Reader as my default PDF reader. With windows 11, only in some cases it doesn't work. Let's say the association is not made on 5% of the computers that I format.
 
According to the author of the tool, it has to do with the build of Windows. Also he told me, that sometimes it takes some time after the latest update to start blocking this change.
 
Wanderer82 said:
According to the author of the tool, it has to do with the build of Windows. Also he told me, that sometimes it takes some time after the latest update to start blocking this change.
Click to expand...
I have noticed that on the latest build of Windows 11, some settings and changes either take a while to stick or are simply overwritten during the user profile creation. It's rather tedious to have to deal with. One method I have used was something proposed by Garlin I believe. It involves creating a RunOnce batch script to automatically run some time after a user logs on for the first time. The delay usually provides a big enough margin of error so that Windows does not meddle with the changes.
 
The user profile is only created once, isn't it? And by saying "it takes some time after the latest update to start blocking this change", I mean that sometimes after the interview the tool for changing the standard webbrowser did work for some short time and only then the new "security feature" or whatever you'd like to call it, gets activated and prevents the tool from working for PDF, HTTP and HTTPS.
 
Wanderer82 said:
The user profile is only created once, isn't it? And by saying "it takes some time after the latest update to start blocking this change", I mean that sometimes after the interview the tool for changing the standard webbrowser did work for some short time and only then the new "security feature" or whatever you'd like to call it, gets activated and prevents the tool from working for PDF, HTTP and HTTPS.
Click to expand...
Yes, well, if you only have one profile. In my use case, I add a couple of profiles to the system, hence the extra precaution. I have not come across the system actively blocking file association changes yet, but I would not be surprised.
 
Wanderer82 said:
According to the author of the tool, it has to do with the build of Windows. Also he told me, that sometimes it takes some time after the latest update to start blocking this change.
Click to expand...
For more technical details:

Workaround:
1. Load the image.
2. Confirm that UCPD is disabled under Services / Extra Services.
3. From Scheduled Tasks, remove task Microsoft Windows / AppxDeploymentClient / UCPD velocity,
4. Apply changes.

UCPD driver should not be enabled on first install. But it's now included in the W11 CU, so you should try changing the FTA's before running Windows Update, or installing the Monthly Updates.
 
You must log in or register to reply here.
Back
Top