Some temp files that have a size of 0 bytes are not deleted automatically after you install or upgrade the printer driver on a Windows Vista or Windows Server 2008-based computer

After you install or upgrade the printer driver on a Windows Vista-based or on a Windows Server 2008-based computer, some temp files that have a size of 0 bytes are created in the following folder:

%SystemRoot%\system32\spool\drivers\w32x86\3

Note The temp files have a name, such as BUD<nnnn>.tmp. The <nnnn> placeholder represents a series of numbers.

Additionally, these temp files are not deleted automatically.

This problem may occur if the newly installed or upgraded printer driver includes the Unidrv.dll driver for Windows Vista or for Windows Server 2008.

The redundant BUD<nnnn>.tmp files are created by the Unidrv.dll driver when the driver is installed or upgraded. If an old BUD<nnnn>.tmp file exists, the function tries to delete the BUD<nnnn>.tmp file. However, if the file is open, the file cannot be deleted. Therefore, a new BUD<nnnn>.tmp file that has a size of 0 bytes is created. Additionally, this file is not accessed by the Unidrv.dll driver. Therefore, these files are not deleted automatically.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the �Hotfix Request� page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix on Windows Vista-based computer, you must have Windows Vista SP1 installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base: There are no prerequisites for Windows Server 2008-based computers.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista and Windows Server 2008 file information notes

The .manifest files and the .mum files that are installed in each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.

For all supported x86-based versions of Windows Server 2008 and of Windows Vista

For all supported x64-based versions of Windows Server 2008 and of Windows Vista

For all supported IA-64-based versions of Windows Server 2008

To work around this problem, manually delete these redundant temp files.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Additional file information for Windows Server 2008 and Windows Vista

Additional files for all supported x86-based versions of Windows Server 2008 and Windows Vista

Additional files for all supported x64-based versions of Windows Server 2008 and of Windows Vista

Additional files for all supported IA-64-based versions of Windows Server 2008