Kinds of WAS Files

Dominant WAS File Type

.WAS

File Name:	.was
File Type:	Symantec Procomm Plus Script

Script file used by Procomm Plus, a terminal emulation and file transfer software. This format is obsolete and no longer supported.

Author:	Symantec Corporation
Class:	Developer Files
Folder:	HKEY_CLASSES_ROOT\.was

Software Programs That Open The Symantec Procomm Plus Script:

Procomm Plus by Symantec Corporation

Windows

Optional Offer for FileViewPro by Solvusoft | EULA | Privacy Policy | Terms | Uninstall

Troubleshoot WAS Files

Troubles Opening WAS Files

Procomm Plus Isn't There

When you double-click your WAS file, you may see a dialog box from your operating system stating that it "Cannot Open This File Type". Usually, this is because you do not have Procomm Plus for %%os%% installed. The typical path of opening your WAS with a double-click won't work because %%os%% cannot make the program connection.

Tip: If you have another software that you know opens WAS files, you can select it by hitting the "Show Apps" button.

Wrong Version of Procomm Plus is Installed

Occasionally, you might have an outdated version of Procomm Plus installed that's incompatible with your Symantec Procomm Plus Script type. Visit the Symantec Corporation website to download (or purchase) the latest version of Procomm Plus. This problem is most common when you have an older version of the software application, and your file was created by a newer version that it cannot recognize.

Tip: Sometimes you can get a clue about the version of WAS file you have by right clicking on the file, then clicking on "Properties" (Windows) or "Get Info" (Mac OSX).

Regardless, most of the WAS file opening problems relate to not having the right version of Procomm Plus installed.

Additional WAS Opening Issues

You can still experience errors opening WAS files even with the latest version of Procomm Plus installed on your PC. There can be external issues inside of %%os%% that are causing these errors when opening WASs. These other problems include (listed in order from most to least common):

• WAS file type Registry entries are wrong
• Mistaken removal of the Windows registry WAS description
• Invalid installation of a WAS-associated program (eg. Procomm Plus)
• Your WAS file is corrupted (issues with your Symantec Procomm Plus Script file itself)
• WAS file integrity has been compromised by malware
• Device drivers of the hardware associated with your WAS file are corrupt or out-of-date
• Windows cannot load your Symantec Procomm Plus Script file due to insufficient resources (eg. RAM)