Since weekend update, small files up to 4096 bytes get cor..

In microsoft.public.win2000.file_system
=?Utf-8?B?QW5keSBTY2htaWR0?= wrote:

> Hi,
>
> I have two different servers (different models and manufacturing
> years), but both of them running Windows 2000 server with
> software mirrored NTFS drives, which suddenly corrupt small
> image thumbnail files after an hour or two.
[ ]

Microsoft Security Bulletin MS06-049
Vulnerability in Windows Kernel Could Result in Elevation of
Privilege (920958)
Published: August 8, 2006 |
Updated: September 26, 2006
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
================== excerpt ======================
V2.0 (September 26, 2006): The update has been revised and re-
released for Microsoft Windows 2000 Service Pack 4 to address
issues identified in Microsoft Knowledge Base Article 920958.
=====================================================

http://www.microsoft.com/technet/security/Bulletin/MS06-049.mspx
This is the patch (v1) for W2K that caused corrupt files in on-disk
Compressed files.

First MS issued a HotFix for W2K 2006-09-15
Then issued those same files via KB-925308 2006-06-20
And finally they have incorporated the files
for W2K back into the "049" package for W2K.

W2K users should apply one of the "corrected files" packages if
they ever installed MS06-049, (920958) version 1.
W2K users that store Security pkg. files locally should update
their stored copy to "version 2".
Windows2000-KB920958-v2-x86-ENU.EXE 1,603,560 bytes
MD5: 09f6b7733eca534b2620549e1e184f7d

All three sources of "corrected files" contain the same 5 updated
files.

"Andy Schmidt" wrote:

> Hi,
>
> I have two different servers (different models and manufacturing years), but
> both of them running Windows 2000 server with software mirrored NTFS drives,
> which suddenly corrupt small image thumbnail files after an hour or two.
>
> No larger file sizes seem to be effected. The file content is set to all
> binary 0xdf.
>
> If we replace those files with valid copies, then those files will appear to
> be correct for a while (probably read back from cache) but after some time
> they will "revert" back to all 0xdf.
>
> I have since been in contact with another customer who has the exact same
> problem with his Windows 2000 server also since around the past weekend. In
> the days prior we did install recent security fixes and Microsoft product
> updates that were released in the past month.
>
> Is there anyone else out there with the same problem?