NotHereToPlayGames

There is no map in Chrome v140 on Win10 either. (for reference)

See here for more - https://help.pdf-xchange.com/pdfxe6/index.html?command-line-options_ed.html I'm afraid that if you find command lines "too confusing" then I'm not going to be able to assist any further. I've provided what the DEVELOPER HIMSELF/HERSELF cites for setting file associations.

Whatever is easiest for you, OPEN AN ADMIN COMMAND PROMPT and direct it to the FOLDER CONTAINING your "PDFXEdit v6.exe". Then perform BOTH of the following (unsure if which is performed first is important or not, this was the order the DEVELOPER indicated): "PDFXEdit v6.exe" /fileassoc:user=no "PDFXEdit v6.exe" /fileassoc:user=yes This really really REALLY should solve your problem - IT IS DIRECT FROM THE DEVELOPER OF PDF-XCHANGE (but the VIEWER instead of the EDITOR, this method is supposed to work for both).

Try this. 1) Open FILE EXPLORER (even if you have alternative file manager, please open FILE EXPLORER) and navigate to your "PDF-Xchange Editor v6 Portable" folder. 2) Click ONCE inside the address bar so that the entire folder PATH is highlighted. 3) Do CTRL-C on keyboard to copy that hightlighted PATH. 4) Now open a COMMAND PROMPT WINDOW *AS ADMIN*. 5) Type "cd " (c d SPACE) without the quotes then CTRL-V then hit ENTER. ie, an ADMIN COMMAND PROMPT from the directory CONTAINING your "PDFXEdit v6.exe" file. 6a) Now do *BOTH* of the following (no!, the second one does not 'replace' the first one, the first one MUST be executed to establish LOCAL MACHINE registry configuration). 6b) In that ADMIN COMMAND PROMPT, enter and execute the following INCLUDING the quotes around the .exe file name: "PDFXEdit v6.exe" /fileassoc:user=no 6c) AFTER doing the above, do the BELOW in that ADMIN COMMAND PROMPT (this sets CURRENT USER registry configuration that is USELESS without the LOCAL MACHINE registry configuration also in place): "PDFXEdit v6.exe" /fileassoc:user=yes 7) REBOOT YOUR COMPUTER - *required* for additions to LOCAL MACHINE and CURRENT USER registry hive changes to *take effect* 8) double-click on a .pdf file and (fingers crossed), it SHOULD launch PDF-Xchange Editor *and* open the file you double-clicked

Here's where I would go next "if it were me". The pop-up box contains a list of programs that are PROPERLY embedded within the OS Registry. Scan that list for something that should be "rare" within the OS Registry, search for THAT PROGRAM in the OS Registry. You should be able to find WHAT populates that pop-up list. Now you know WHERE to ADD your preferred pdf file "handler". edit - I kind of have to assume that you have a PATH issue, you are associating pdf files with an EXE (with spaces in the name!) but nowhere is the PATH (also containing spaces!) to that EXE being defined. SPACES have a way of "breaking" things if not properly accomodated for. Why "all of this" is just now hitting your setup is definitly a mystery. My assumption is a "registry cleaner" was used, but that is just an assumption.

There *MUST* be something different between the two OS Registries (not to state the obvious, as I'm sure you already know this). Many associations are much more complicated than "OpenWithList". I guess all I can suggest at this point is to search for any-and-all pdf ocurrences in that 2nd W7 Pro's registry and compare to the computer where you are having the issues. There's (obviously) something different between the two and it basically "has to be" at the registry-level. ps - I can't help but "laugh" when BACKUPS contain issues that the backup was resorted to in order to FIX the non-backup. not laughing "at you", laughing because this happens at work *ALL THE TIME*, "backups" are never TESTED and when they go to get USED, the department finds them to be *USELESS*.

There isn't supposed to be. A true "portable" will *NOT* be associated. If you want the association, you should probably be using the "regular" version instead of the "portable" version. "Portable" versions are generally for people that do *NOT* want the file associations. Your list does *NOT* narrow things down for me, they all do not create the "bin" / "profile" the same way. But if you do not have any issues running the program THEN opening a .pdf, then your "bin" / "profile" SHOULD be okay (ie, not corrupted). Again, if you want OS-Level ASSOCIATIONS, you technically shouldn't be using the PORTABLE version. Because there are "mime types" and GUIDS and CLSIDS and ProgIds and namespaces and file PATHS and other things to also "associate" above-and-beyond a simple "OpenWithList". ie, things that over-simplified "registry cleaners" would have wiped clean and all you are trying to bring back is the "OpenWithList" - won't *always* be enough (sometimes it is).

Not sure on Win7, but never trust an Uptime claim on Win10. Why? Because you can "hibernate" and then leave the computer in the attic for DECADES. Then launch it DECADES later and the "uptime" will SAY it has been "up" for that ENTIRE time.

Do you have a link of where you obtained PDF-Xchange?

I have an FM Transmitter that I've modified to "jam" any radio within 50 feet. Overrides a local FM radio station and plays DEAD SILENCE instead. Not sure if I'm breaking any FCC rules or not. BUT it is a GODSEND for my SANITY! Why? Because I do not (and will not!) listen to COUNTRY MUSIC !!! :)

It's not that bad, IF you tweak the CRAP out of it! I strongly (strongly!) suggest learning how / teaching yourself how to create installation media that removes the CRAP *BEFORE* the install! Do not (do not!) install FIRST then remove the crap LATER. You GOTTA remove the crap FIRST. There are some very good "scripts" (PowerShell) that make "decent" attempts at removing AFTER-THE-FACT (install first, remove later), but you really are BETTER-SERVED in not allowing the bloat to be installed in the first place. Install first then remove later method always (always!) leaves a "tangled mess" of a Windows Registry behind. For your radio station needs, I suspect that Win10 *1511* is really all that you need. I currently stick with *1607* and *21H2* the best I can (hardware-dependent). Good Luck! Don't "fear" Win10. Fear the BLOAT of "standard user, default installs", but don't fear The De-Bloated Advanced-User. Oh, last but not least, do not (do not!) save yourself legwork by using anything called "tiny" or "lite" or the names creatively change more than the underlying "debloatifying". Just trust me, you will NOT be satisfied unless YOU do the legwork. But do be warned, there *IS* a "learning curve". But I have no doubt whatsoever that you are smart enough to take on the task.

I would certainly recommend that over any "AI-generated" list! We are YEARS away from "AI" being a trusted and reputable source! In my not-so-humble opinion. AI, for now, is nothing but "Junk in, junk out". I get some reasonably good STARTING POINT javascript code from AI, but it is NEVER perfect or good-to-go without HUMAN intervention.

I'm not familiar with "PDF-Xchange", but your screencap cites it as PORTABLE. So what happens if you copy the folder (archive it somewhere), then DELETE the portable apps "profile" then launch it? Just speculating as all of my portable apps have their own "bin" (profile) where files and registry is saved within itself (as opposed to Win Registry / Program Files Folder / User Data Directory / etc). ie, force PDF-Xchange to start BRAND NEW / FIRST-RUN.

Is it IE5 or a different web browser? Seems to me it's an IE setting telling it to use %TEMP%.

Copy the FOLDER NAME, delete the FOLDER, then create a *FILE* with the same exact NAME but *without* any file extension. Windows will not allow a FOLDER and a FILE by the same exact NAME. The presence of the FILE *prevents* the folder of the same name from being created. ie, you will never have to delete the folder ever again because it cannot be created.