WinFax PRO Support

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.

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.

This error message can occur with version 10.02 and higher of WinFax PRO that is operating in the Windows XP environment.  It does not appear under Windows 2000 or windows 9x environments, or versions 10.0 or 10.01. To determine the version of WinFax PRO you are using, click “WinFax Info” button in WinFax Tools.

Usually, starting the WinFax Controller may correct this problem, in some scenarios you may need to reboot of the computer.  If this does not solve the problem, then your installation of WinFax is likely corrupt and needs repair.

If you continue to encounter this error we recommend using the “Fix Start Up Errors” option in WinFax Tools.

Sometimes a fax can appear stuck or faxes fail to send when you submit them. This can be caused due to corruption in the default WinFax send, receive and outbox log.

Repairing a log or phonebook database in WinFax can now be accomplished with ease using WinFax Tools.

Before rebuilding any data in WinFax please backup your entire DATA folder (or entire WinFax folder) where all your WinFax files are located.  We recommend this in case of any failure during the rebuild/repair process.  If you’re not sure where your WinFax files are located, WinFax Tools can determine the location of your DATA folder for you, click on WinFax Info. Read the rest of this entry »

If you’ve just upgraded to Internet Explorer 8, and now WinFax PRO 10 is no longer working as it should (closes when entering phone numbers, fails during an install when entering the CSID, or fails entering number of rings for automatic answer) then see the following link: WinFax PRO and Problems with SP2, SP3, IE7 or IE8

Many of you held off upgrading from XP to Vista are considering the upgrade to Microsoft’s latest operating system Windows 7, 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, Windows 7, doesn’t change the compatibility issues with WinFax PRO that were introduced with Microsoft Vista.  As expected, the same compatibility issues with WinFax PRO and TalkWorks PRO also exist with Windows 7. Read the rest of this entry »