What To Do When Microsoft Word Says The Directory Name Is Not Valid
What Does It Mean When Microsoft Word Says The Directory Name Is Not Valid
Microsoft Word The Directory Name Is Not Valid

Office 2007 Pro on Windows XP pro. Tried to use 'Edit with Microsoft Office Word' from the File menu of a webpage (IE8). I was met with a message saying 'The Directory name is not valid (C: Documents and Settings profile Desktop)'.
Check the Administration System Initialization General Settings Path tab for the definition of a proper path to the Word directory. Help to improve this answer by adding a comment. If you have a different answer for this question, then please use the Your Answer form at the bottom of the page instead.
Copy the folder from the USB Drive to the local hard disk (NOT the desktop) and then open that folder on the hard disk and see if the document is there. If it is, use FileOpen in Word and browse to that folder and select the document. DO NOT OPEN THE DOCUMENT WHILE IT IS ON THE USB DRIVE AS IT IS VERY LIKELY TO BECOME CORRUPTED IF YOU DO THAT.

An underscore is permitted anywhere in the user name. This includes at the beginning or end of the name. When creating a group, the number sign (#) can be used as part of the group's name. However, the email address you create for a distribution group or shared mailbox cannot use the # sign. Mar 19, 2019 Please try to open Word in Safe Mode to have a check: Press Windows + R to start Run, type the command winword /safe in the box. After you open Word in Safe Mode, click File Open to open a document in Word. Does the issue still occur? Please try to reset your Word options and registry settings to have a check.

-->

Use these suggestions to troubleshoot problems you experience when packaging, deploying, or querying a Windows app package (.msix/.appx) as a developer.

Note

This article is intended for developers. If you are not a developer and you are looking for help with a Windows app installation error, see Windows support.

Get diagnostic information

When an API fails, it returns an error code that describes the problem. If the error code doesn't provide enough information, you find more diagnostic information in the detailed event logs.

To access the packaging and deployment event logs by using Event Viewer, follow these steps:

Perform one of the following steps:
- Click Start on the Windows menu, type Event Viewer, and press Enter.
- Run eventvwr.msc.
In the left page, expand Event Viewer (Local) > Applications and Services Logs > Microsoft > Windows.
Check for available logs under these categories:
- AppxPackagingOM > Microsoft-Windows-AppxPackaging/Operational
- AppXDeployment-Server > Microsoft-Windows-AppXDeploymentServer/Operational

Start by looking at the logs under AppXDeployment-Server. If the error was caused by 0x80073CF0 or ERROR_INSTALL_OPEN_PACKAGE_FAILED, additional details may be present in the AppxpackagingOM logs.

You can also use the Get-AppxLog command in PowerShell to get the first few logged events. The following example displays the logs associated with the most recent deployment operation.

The following example displays the logs associated with the most recent deployment operation in an interactive table in a separate window.

Common error codes

This table lists some of the most common error codes. If you need further help with one of these errors, or if you're encountering an error code not in this list, see additional help options.

Error code	Value	Description and possible causes
E_FILENOTFOUND	0x80070002	File or path is not found. This can occur during a COM typelib validation requires that the path for the directory actually exist within your MSIX package.
ERROR_BAD_FORMAT	0x8007000B	The package isn't correctly formatted and needs to be re-built or re-signed. You may get this error if there is a mismatch between the signing certificate subject name and the AppxManifest.xml publisher name. See How to sign an app package using SignTool.
E_INVALIDARG	0x80070057	One or more arguments are not valid. If you check the AppXDeployment-Server event log and see the following event: 'While installing the package, the system failed to register the windows.repositoryExtension extension due to the following error: The parameter is incorrect.' You may get this error if the manifest elements DisplayName or Description contain characters disallowed by Windows firewall; namely \| and all , due to which Windows fails to create the AppContainer profile for the package. Please remove these characters from the manifest and try installing the package.
ERROR_INSTALL_OPEN_ PACKAGE_FAILED	0x80073CF0	The package couldn't be opened. Possible causes: The package is unsigned. The publisher name doesn't match the signing certificate subject. The file:// prefix is missing or the package couldn't be found at the specified location. For more information, check the AppxPackagingOM event log.
ERROR_INSTALL_PACKAGE_ NOT_FOUND	0x80073CF1	The package couldn't be found. You may get this error while removing a package that isn't installed for the current user.
ERROR_INSTALL_INVALID_ PACKAGE	0x80073CF2	The package data isn't valid.
ERROR_INSTALL_RESOLVE_ DEPENDENCY_FAILED	0x80073CF3	The package failed update, dependency, or conflict validation. Possible causes: The incoming package conflicts with an installed package. A specified package dependency can't be found. The package doesn't support the correct processor architecture. For more informtion, check the AppXDeployment-Server event log.
ERROR_INSTALL_OUT_ OF_DISK_SPACE	0x80073CF4	There isn't enough disk space on your computer. Free some space and try again.
ERROR_INSTALL_NETWORK_ FAILURE	0x80073CF5	The package can't be downloaded.
ERROR_INSTALL_ REGISTRATION_FAILURE	0x80073CF6	The package can't be registered. For more information, check the AppXDeployment-Server event log.
ERROR_INSTALL_ DEREGISTRATION_EFAILURE	0x80073CF7	The package can't be unregistered. You may get this error while removing a package. For more information, check the AppXDeployment-Server event log.
ERROR_INSTALL_CANCEL	0x80073CF8	The user canceled the install request.
ERROR_INSTALL_FAILED	0x80073CF9	Package install failed. Contact the software vendor. For more information, check the AppXDeployment-Server event log.
ERROR_REMOVE_FAILED	0x80073CFA	Package removal failed. You may get this error for failures that occur during package uninstall. For more information, see RemovePackageAsync.
ERROR_PACKAGE_ ALREADY_EXISTS	0x80073CFB	The provided package is already installed, and reinstallation of the package is blocked. You may get this error if installing a package that is not bitwise identical to the package that is already installed. Note that the digital signature is also part of the package. Hence if a package is rebuilt or resigned, it is no longer bitwise identical to the previously installed package.

Microsoft Word The Directory Name Isnt Valid