Welcome to the first and only dedicated Web site for WinFax PRO faxing software from Symantec/Delrina. We offer a free community based forum for WinFax PRO, plus premium members have access to our exclusive WinFax Tools automated diagnostic and repair tool, support via forums, compatibility fixes, downloads and access to all archived postings.
You can also get professional WinFax Live Remote Support Services from a knowledgeable WinFax tech.
Support the WinFax community and become a WinFax Premium Subscriber You'll have access to all the WinFax support forums and exclusive WinFax Tools program to troubleshoot WinFax issues for only $29.99 (US$) per year. Click the links above for more details.
Visit the WinFax technical support Forums here: WinFax Community Support Forums
|
|
WinFax PRO alternative faxing software for Microsoft Windows February 19th, 2010
FaxTalk software is available in three different versions depending on your needs, FaxTalk FaxCenter Pro as a replacement to WinFax PRO for faxing, FaxTalk Messenger Pro, as a replacement for TalkWorks PRO (it is WinFax with voice support if you have the proper fax/voice modem) and FaxTalk Multiline Server (a networking fax software that supports up to 8 fax modems at once, a replacement for WinFax PRO Fax Sharing)
Posted in Guides, Support | Comments Closed
WinFax PRO and Windows Server 2003/Windows Server 2008 November 23rd, 2009
One of the main components of WinFax PRO is its printer driver, the printer driver allows you to fax from other applications. Without this driver, you cannot send faxes from other applications. WinFax PRO is crippled without the installation of the included printer (WinFax) driver, without it, all you can fax are single cover pages that are built into WinFax.
Windows Server 2003
The first problem with installation of WinFax PRO under Windows 2003 is that the printer driver support in the operating system was moved from kernel to user mode. The reason is that the use of kernel mode printer drivers can possibily cause a server to hang, result in a blue screen and require a reboot. This isn’t something you want happening on a server. Because of this possibility, Microsoft decided to block the installation of all kernel mode printer drivers in Windows 2003. During the installation of WinFax PRO, a kernel mode printer driver (also called version 2 printer driver) is added to your list of installed printers. By default, Windows 2003 won’t allow you to add this printer, and during the installation it is either ignored silently or a printer driver related error message is displayed. Fortunately, in Windows 2003 you can bypass this restriction. You can set a group policy in Windows 2003 to allow the installation of kernel mode printers. Once you’ve done this, you should be able to successfully install WinFax PRO under Windows 2003.
Windows Server 2008
Windows Server 2008 does not support Type 2/Kernel Mode printer drivers. While the installation of WinFax (may) appear to complete under Windows 2008, the installation will not include these printer drivers. WinFax PRO is not compatible with this operating system.
How to detect a counterfeit WinFax PRO 10 CD ROM September 14th, 2009
Don’t get duped into buying a counterfeit WinFax PRO 10 CD ROM. Here is how you can tell the difference from a “real” CD ROM and the obvious fakes. If you purchased your Symantec WinFax PRO with a box and manual, chances are it is the genuine item. If you purchased a “loose” CD ROM, usually referred as “OEM”, then you should check for the following:
- Symantec never included the actual revision of WinFax PRO 10 (10.01,10.02 or 10.03) on the CD ROM. So, if your WinFax PRO CD ROM says “WinFax PRO 10.03″ its a fake. All genuine WinFax PRO 10 cd’s contain the heading ”WinFax PRO 10.0″
- If you see text with “winFAX” or “Live Update” anywhere on the CD its a fake. The official Symantec trademarks are ”WinFax” and “LiveUpdate”, no other variations of this text should appear on the CD ROM.
- Failure to capitalize ”symantec” and “corporation”.
- An “All rights resverd” spelling error, or other spelling errors.
- Incorrect font used for WinFax PRO and Symantec logo. The current Symantec logo is consistant across all software they produce.
- Silver portion of CD is a (dull) matte finish, on the real CD it is relective (mirror surface).
- To determine if the CD is brand new and sealed – geniune WinFax PRO 10 CD’s come in a white envelope sleeve that are sealed with a sticker that may have one or more of the following: a bar code, a Symantec 5 or 6 digit product code, a brief license agreement.
- In most cases, manufacturer information is printed on the inner rim of the CD ROM of genuine CD’s. This is usually missing on a counterfeit.
- Update patch 10.04 is not included on genuine CD ROMs. Any CD that contains the patch update to 10.04 is a counterfeit.
Example of a counterfeit CD ROM and genuine WinFax PRO 10 CD ROM. Notice the differences in the mirror surface, the Symantec logo, and different font types. The counterfeit contains ”10.03″ version, something that is not printed on the genuine CD. You’ll also probably see manufacturer information around the inner rim of the genuine CD ROM. This is likely to be missing on the counterfeit WinFax PRO CD.
This is a counterfeit poor quality copy of WinFax PRO 10.03 that appears to be created on a home deskjet printer. Note the non-reflective matte finish on the CD ROM.

Here is the original design of the WnFax PRO 10 CD ROM used for North American releases of WinFax PRO 10.0 and WinFax PRO 10.01. This has a different design, yellow with silver (reflective) images. This version uses the older style Symantec logo.

This image on the left is an example of a genuine WinFax PRO 10.0 or 10.01 CD ROM. Symantec updated most of its design & software boxes when they changed logo designs. Version 10.02 and 10.03 use the updated design & Symantec logo. This design also uses a reflective mirror finish on portions of the CD ROM. Lack of reflective mirror finish would indicate a counterfeit CD, or a version with the 10.04 update included on the same install CD would indicate a counterfeit.
WinFax PRO Security Update for ActiveX control August 15th, 2009
An ActiveX security flaw has been detected in the WinFax PRO Viewer Control. This bulletin applies to the following versions of WinFax:
- WinFax PRO 8.0x
- WinFax PRO 9.0x
- WinFax PRO 10.0x
- TalkWorks PRO 2.0x
- TalkWorks PRO 3.0
- WinFax Basic Edition (all versions)
- TalkWorks Basic Edition (all versions)
- Delrina Fax (French release, version 8.0x and above)
More details on this security flaw by clicking here
Symantec has released this official Security Bulletin for WinFax PRO, technical details can be found at Symantec’s Web site
If you use a Norton product for security, such as Norton 360 and Norton Internet Security 2009, this threat is detected with current definitions. Other security software from other vendors may also detect this threat.
Regardless of the type of security you are using, We recommend setting the KillBit for this specific ActiveX control to always prevent it from activating. Setting this KillBit does NOT effect the normal operation of WinFax PRO.
This is recommended if you have or do not have an installation of WinFax PRO.
If you have prior experience in setting a KillBit in the Windows registry, the CSLID for the WinFax PRO Viewer Control is {C05A1FBC-1413-11D1-B05F-00805F4945F6}
or, you can use our tool to do this for you, download our Free version of WinFax Tools. Click “Fix Security DLL” button and the KillBit will be set automatically.
UPDATE: In a Windows XP update that was released February 9th, 2010, this security flaw was finally addressed. The actual update released by Microsoft is: Microsoft Security Bulletin MS10-008 – Critical Cumulative Security Update of ActiveX Kill Bits (978262). If you have already downloaded this security update for Windows XP, then your system will already have the necessary ActiveX Kill bits set for the WinFax PRO ActiveX control. You can still download WinFax Tools and confirm if the ActiveX kill bit was applied properly by this Windows XP Update. If your system has the Killbit set, the WinFax Tools program will indicate it has already been applied.
Unable to locate the installation log file WFXUNIST.ISU July 20th, 2009
Error message: “Unable to locate the installation log file C:\Program Files\WinFax\WFXUNIST.ISU” during WinFax PRO uninstallation or “WFXUNINST.ISU is missing or corrupt.”
This is an error that causes an uninstall of WinFax PRO to fail. This file is an uninstallation log file that is generated by a third party installation tool called Install Shield. Its automatically generated when you first installed WinFax PRO, so you won’t find this file on the WinFax PRO installation CD ROM. This log file contains all the information and settings that the uninstall program requires to remove WinFax, such as the program folder locations and features that you added or removed during the install process. Read the rest of this entry »
Symantec WinFax PRO and Microsoft Windows 7 compatibility June 3rd, 2009
Many of you held off upgrading from Windows XP to Windows Vista and are considering the upgrade to Microsoft’s latest operating system Windows 7 (or even the new Windows 8), but are wondering if many of your existing applications such as WinFax PRO will work.
WinFax PRO and TalkWorks PRO (the fax/voice version of Symantec’s popular fax software) still have a strong user base and many of you don’t want to give up this powerful and easy to use desktop faxing software.
Unfortunately Microsoft Windows 7, along with the upcoming Windows 8 are NOT compatible with WinFax PRO. Read the rest of this entry »
Security flaw found in ActiveX Control used by Symantec's WinFax PRO April 30th, 2009

An important update to all WinFax PRO fax users
UPDATED NEWS : Microsoft releases “ActiveX Killbits” Security Patch for XP February 9th, 2010 (See below)
A security flaw (called a Remote Buffer overflow) with a specific ActiveX Control that is used by WinFax PRO was reported. This type of security flaw is fairly common with ActiveX controls, and effects many programs out there. Recently the same security risks were identified in Facebook & Yahoo Music ActiveX controls. The flaw allows a script (on a Web page that you visit) to execute a program on your computer. When these risks are identified, Microsoft releases a security update to the operating system that fixes these holes. Read the rest of this entry »
Posted in Guides, Setup, Support | Comments Closed
