Valid pdf file names

Luckily the error doesn't appear that often and everyone has been able to work around it. Anyone else run into this error in Outlook? I have the same question Report abuse.

Details required :. Cancel Submit. Hi jd92 Greetings Thank you for posting in Microsoft Community. PDF file names should be less than 50 characters, including punctuation and spaces.

File names can contain any of the following characters: A-Z, a-z, , underscore, hyphen, space, period, parenthesis, curly braces, square brackets, tilde, exclamation point, comma, semicolon, apostrophe, at sign, number sign, dollar sign, percent sign, plus sign, and equal sign. While single spaces are allowed between words or characters in the file name, do not use two or more spaces in a row between words or characters as this will cause errors.

The list of acceptable characters above includes apostrophes. Popular Topics in Windows Spiceworks Help Desk. The help desk software for IT. Track users' IT needs, easily, and with only the features you need. Learn More ». Pure Capsaicin. Windows 10 expert. Can you check one of the files, is it trying to save as filename.. Notice the double dot? Users can remove one and save it, but this is a patch issue, it was revoked, then re-released.

This KB may not be the exact one, a later one caused a similar issue. All English. Also, I have tried these things: changing the file name to something of my own in the save dialog explicitly defining the appropriate file extension.

Are the locations for the save local or network? Only happening from the internet too? Do all machines apply the same GPO? Here is the error. Only 2 applications with the issue and that is Chrome and Outlook. I just tried opening a pdf in Chrome that is on the local machine and it still has the same issue when trying to save it.

However, Edge works fine on anything. Can you also try Chrome in incognito mode, does it still happen? Examples of this format are as follows:.

A path is also said to be relative if it contains "double-dots"; that is, two periods together in one component of the path. This special specifier is used to denote the directory above the current directory, otherwise known as the "parent directory". Relative paths can combine both example types, for example "C This is useful because, although the system keeps track of the current drive along with the current directory of that drive, it also keeps track of the current directories in each of the different drive letters if your system has more than one , regardless of which drive designator is set as the current drive.

In later versions of Windows, changing a registry key or using the Group Policy tool is required to remove the limit. See Maximum Path Length Limitation for full details. There are two main categories of namespace conventions used in the Windows APIs, commonly referred to as NT namespaces and the Win32 namespaces.

The NT namespace was designed to be the lowest level namespace on which other subsystems and namespaces could exist, including the Win32 subsystem and, by extension, the Win32 namespaces. Early versions of Windows also defined several predefined, or reserved, names for certain special devices such as communications serial and parallel ports and the default display console as part of what is now called the NT device namespace, and are still supported in current versions of Windows for backward compatibility.

The Win32 namespace prefixing and conventions are summarized in this section and the following section, with descriptions of how they are used. Note that these examples are intended for use with the Windows API functions and do not all necessarily work with Windows shell applications such as Windows Explorer.

For this reason there is a wider range of possible paths than is usually available from Windows shell applications, and Windows applications that take advantage of this can be developed using these namespace conventions. For more information about the normal maximum path limitation, see the previous section Maximum Path Length Limitation. This is how access to physical disks and volumes is accomplished directly, without going through the file system, if the API supports this type of access.

You can access many devices other than disks this way using the CreateFile and DefineDosDevice functions, for example. For example, if you want to open the system's serial communications port 1, you can use "COM1" in the call to the CreateFile function. This allows you to access those devices directly, bypassing the file system.

This works because these device names are created by the system as these devices are enumerated, and some drivers will also create other aliases in the system. Always check the reference topic for each API to be sure. To illustrate, it is useful to browse the Windows namespaces in the system object browser using the Windows Sysinternals WinObj tool.

The subfolder called "Global?? Named device objects reside in the NT namespace within the "Device" subdirectory.