Registry Data Is Viewable By All Users During Rdisk Repair Update

View products that this article applies to.

This article was previously published under Q249108

SYMPTOMS

When you use the Rdisk tool to update the repair information on a computer that is running Windows NT 4.0, a temporary file is created that enumerates all of the registry hives and their current settings. The permissions on this file do not prevent anyone from reading or changing the temporary file's contents while Rdisk is running.

When the Rdisk tool completes the update procedure, the temporary file is deleted. However, if the Rdisk tool is interrupted or ends abnormally (requiring a restart), the file may still be accessed after the computer is rebooted. The file can also be read while the Rdisk tool is running.

Back to the top

RESOLUTION

Windows NT 4.0 and Windows NT 4.0, Enterprise Edition

To resolve this problem, obtain the individual package referenced below or obtain the Windows NT 4.0 Security Rollup Package. For additional information on the SRP, click the article number below to view the article in the Microsoft Knowledge Base:

299444 (http://support.microsoft.com/kb/299444/EN-US/ ) Post-Windows NT 4.0 Service Pack 6a Security Rollup Package (SRP)

The following files are available for download from the Microsoft Download Center:

x86:

Collapse this imageExpand this image

Download Q249108i.exe now (https://www.microsoft.com/Downloads/details.aspx?displaylang=en&FamilyID=163B4FEF-DF1C-43AF-B4F0-CF91BBB42FA6)

Alpha:

Collapse this imageExpand this image

Download Q249108a.exe now (http://www.microsoft.com/Downloads/details.aspx?displaylang=en&FamilyID=216C913B-27E6-48DE-B61B-04638593B51A)

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 (http://support.microsoft.com/kb/119591/EN-US/ ) How to Obtain Microsoft Support Files from Online Services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file. The English version of this fix should have the following file attributes or later:

   Date         Time     Size      File name   Platform
   ----------------------------------------------------
   01/02/2000   03:35p    68,368   Rdisk.exe   x86
   01/02/2000   03:34p   137,488   Rdisk.exe   Alpha

Back to the top

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 (http://support.microsoft.com/kb/152734/EN-US/ ) How to Obtain the Latest Windows NT 4.0 Service Pack

The following file is available for download from the Microsoft Download Center:

x86:

Collapse this imageExpand this image

Download Q249108i.exe now (https://www.microsoft.com/Downloads/details.aspx?familyid=45115036-D197-4B82-89EB-87ABC17CB3F8&displaylang=en)

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 (http://support.microsoft.com/kb/119591/EN-US/ ) How to Obtain Microsoft Support Files from Online Services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on secure servers that prevent any unauthorized changes to the file.

Back to the top

STATUS

Windows NT 4.0 and Windows NT 4.0, Enterprise Edition

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Back to the top

Windows NT Server 4.0, Terminal Server Edition

Microsoft has confirmed that this problem may cause a degree of security vulnerability in Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.

Back to the top