... and I am not referring to the distinction between hand and select tool. I am referring to another problem:

I have set my own cursor scheme for Windows (Lefty Scheme) in Windows system settings. Every application accepts that but Adobe Reader. Whenever using the reader the mouse changes from a white arrow pointing to the upper right corner (lefty scheme) to a black arrow pointing to the upper left corner.

How can I change this? I want the Reader to use the Windows System setting.

I am using Windows 10 Pro 64 Bit, Version 1709, OS Buils 16299.431 and Adobe Reader 2018.011.20038

Many thanks for your help. Much appreciated

With the introduction of virtual desktops in Windows 10, some users such as myself have multiple projects going on simultaneously. The virtual desktop feature greatly aids compartmentalization in this aspect.

Let us say I am working in a virtual desktop called vd3 for instance, and I do not currently have an instance of Acrobat running on vd3. Now I open a PDF file and there is already an instance of Acrobat running on a different virtual desktop, say vd1. Now, instead of opening a new instance of Acrobat in vd3, Windows forces a switch to vd1 and opens my PDF in a new tab in the instance of Acrobat on vd1 instead of in a new instance on vd3. This impacts productivity.

If there is already an instance of Acrobat open in the current virtual desktop, then this works as expected: a new tab is opened in the instance of Acrobat in the current virtual desktop. However, one must first manually remove a tab from an existing instance and then move that new instance to a new virtual desktop and this can become a nuisance.

It would be a good quality of life upgrade if a new instance of Acrobat was automatically started in the current virtual desktop if there is not an instance of Acrobat already running.

Hello. We have a situation where a Windows protocol handler product is used to open documents from an EDRMS. At some point Adobe has apparently changed how it opens links. Now it simply passes a link to the system's default browser on the command line. As as some browsers (notably Chrome and recent builds of Edge which are based on Chromium) don't handle protocol handler URLs from the command line, this style of link now fails to activate.

Links will be of a form similar to example://12345/open but I think this is an issue for all Windows protocol handlers.

ENVIRONMENT:

Windows 10,
Adobe Acrobat Reader DC 2021.001.20145, and
Chrome 89.0.4389.90 (64 bit) as the system's default browser.

STEPS TO REPRODUCE:

(1) Create and register a Windows Protocol Handler. (Example instructions: https://medium.com/swlh/custom-protocol-handling-how-to-8ac41ff651eb )

(2) Make sure Chrome is the system's default browser.

(3) Create a PDF which includes a hyperlink to open a URL of the registered protocol's form.

(4) Confirm that the protocol handler activates and does its thing when pasted into the Windows Start/Run dialog. (This is just to confirm that it's registered properly as far as Windows is concerned.)

(5) Open Adobe Acrobat Reader DC, disable "Enable Protected Mode At Startup" under the Enhanced Security preferences, and restart Adobe Acrobat Reader DC.

(6) Open the PDF that was created in step 3.

(7) Click the protocol handler's link, and click through any warnings.

EXPECTED RESULT:

• The protocol handler should be run according to the link that was clicked. (In our own case, the designated executable should go to the EDRMS and cause the document to be checked out and opened.)

OBSERVED RESULT:

• A blank Chrome browser window opens.
• Interrogating the process list with Powershell indicates that the new Chrome window was opened with the protocol handler's URL on the command line. For example:

PS C:\WINDOWS\system32> Get-CimInstance win32process | Where-Object {$.Name -eq "chrome.exe"} | Select-Object CommandLine

CommandLine

"C:\Program Files\Google\Chrome\Application\chrome.exe" --single-argument example://12345/open
"C:\Program Files\Google\Chrome\Application\chrome.exe" --type=crashpad-handler "--user-data-dir=C:\Users\usernm\AppData\L...
"C:\Program Files\Google\Chrome\Application\chrome.exe" --type=gpu-process --field-trial-handle=1660,1197437607337992284,2...
"C:\Program Files\Google\Chrome\Application\chrome.exe" --type=utility --utility-sub-type=network.mojom.NetworkService --f...
"C:\Program Files\Google\Chrome\Application\chrome.exe" --type=utility --utility-sub-type=storage.mojom.StorageService --f...
"C:\Program Files\Google\Chrome\Application\chrome.exe" --type=renderer --field-trial-handle=1660,1197437607337992284,2916...
"C:\Program Files\Google\Chrome\Application\chrome.exe" --type=renderer --field-trial-handle=1660,1197437607337992284,2916...
"C:\Program Files\Google\Chrome\Application\chrome.exe" --type=renderer --field-trial-handle=1660,1197437607337992284,2916...

ADDITIONAL:

If Firefox or MSIE was set as the default browser, then the browser opens. It typically displays an additional warning, but still allows the protocol handler to be activated. This is consistent with those browsers' behaviour when a non-http link is provided on the command line.

Ideally, if there's no compelling reason not to, I think Adobe Reader should be telling the OS to handle the protocol handler links instead of the default browser. It might be that this will still fail when Adobe Reader is running in Protected Mode, but we're making a conscious decision to run it without protected mode in some contexts so that we can use these links.

Thanks.

Hello, I have found a bug. When in the following configuration:

• Read Mode OR Fixed-width scrolling
• Viewing two pages at once (i.e. bottom of one page and top of the next page are both visible on screen)
• Using the touchscreen of my 2-in-1 (HP Elitebook G4 if that's relevant) to highlight text

I am able to tap once to select a word on either page, but one one of the two pages, I am not able to alter that selection (i.e. grab the little handles at either end of the selection and expand it to include more text). Instead, it treats the gesture as if I am using the pan tool, and attempts to scroll left/right (and if I drag up/down on the handles the page scrolls without changing the selected text).

Upon some experimentation I found that:

• I have no problems using the touchscreen to select text when viewing a single page (in any view mode). I assume Reader is somehow detecting the "active" page, maybe the one most visible on the screen or something, and treating touchscreen gestures on the two pages differently.
• When I use the trackpad/cursor to select text (in read mode or fixed-width scrolling), there is no problem and I am able to adjust the selection. It's only using the touchscreen.
• If the word I initially select is on the "active" page I am able to drag the selection handle to select text over both pages, but not when the initial selected word is on the "inactive" page.

A relatively uncommon scenario for most users I think, but it's juuust disruptive and irritating enough to prompt me to post about it here (and yes, I'm aware I've spent longer typing this bug report than the cumulative time the bug will take from me! Please fix so that the time can at least be a martyr for all touchscreen users time!) :)

When double clicking a file in Windows Explorer where the path is longer than 260 characters does not work as default. But I have been able to create a workaround that enable this.

If I type the following in cmd.exe:
AcroRd32.exe "C:\Very long path\file.pdf" then that will fail.

If I enable "Enable Win32 long paths" in Group Policy and try the same command, then it works. This means that long paths are supported when it is enabled in Windows.

I created a bat-file like this:
set str=%1
set str=%str:\?=%
AcroRd32.exe %str%

This will remove \?\ from the first argument and launch AcroRd32.exe with the trimmed argument.

I changed the registry key HKEYCLASSESROOT\AcroExch.Document.DC\shell\Read\command\ to use this bat-file. And now it works!

It looks like the problem is that Acrobat Reader does not understand if the path start with \?\ but Windows will add this to the start of long filenames.

Information about \?: https://docs.microsoft.com/en-gb/windows/win32/fileio/naming-a-file?redirectedfrom=MSDN

NOTE! I'm writing backslash, backslash, questionmark, backslash. But after posting it only shows \?\

I have a Microsoft Word file that has custom page size specified in the layout (specifically width 6.14" height 9.14"). There are also custom margins. When I convert to pdf via File > Print > Microsoft Print to PDF a pdf file is created but the page size is not correct. A pdf file is created that is 8.5"x11" not 6.14"x9.21". After trying to debug and spending 6+ hours with Microsoft tech support, there seems to be a problem on the Adobe side when the Word file is passed to Adobe to be converted into a pdf. I have noticed that it will convert standard page sizes like letter, legal, etc. But it doesn't work for any custom page sizes (I have tried several different sizes as well as Word page document length and the result is the same each time, Adobe always creates a pdf file that is 8.x5"x11").