Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.network_web,microsoft.public.windowsxp.security_admin (
More info?)
I discovered something very interesting about the Feb 8th kb885250 security
patch bug (where it arbitrarily makes files on certain shared folders
invisible). If the problem folder is renamed, the files appear and
disappear depending on the length of the rename; however, it is hard to
discern a pattern:
Example: These are all folders under the share \\main\c\archive\
Files become INVISIBLE:
asante.firmware\firmware.v_2.5
asante.firmware\firmware.v_2.9
asante.firmware\firmware.v_3.5
asante.firmware\firmware.v_a.b
asante.firmware\firmware.vca.b
asante.firmware\firmware._
asante.firmware\12345678901234
asksam
asksam___ [3 underscore]
asksam____ [4 underscores]
utils
utils2
utilsa
utils____ [4 underscores]
Files become VISIBLE:
asante.firmware\firmware.v_
asante.firmware\firmware.2.5
asante.firmware\firmware.v_2.50
asante.firmware\firmware.v_2.5.t
asante.firmware\firmware.v_2.5.test
asante.firmware\123456789012345
asksam_ [1 underscore]
asksam__ [2 underscores]
asksam_____ [5 underscores]
utilsoth
utilsab
utils25
utils250
utils__ [2 underscores]
utils___ [3 underscores]
"Jeffrey" <Jeffrey@discussions.microsoft.com> wrote in message
news:CE8857D8-3001-4EE1-9447-DA0D45BB9007@microsoft.com...
>I places an email support request for Windows XP SP2 at
> http://support.microsoft.com/oas/default.aspx?&c1=509&gprid=6794&
> In their latest responce they suggested I send in a feature request to the
> Microsoft Wishlist, so I sent a request there also that they fix update
> KB885250 (Removing this one also removes the proble). Since my company
> doesn't carry any Intel I haven't been tested with those either. I'm
> hoping
> that they are not truly understanding what their update did. With wishlist
> addesss is mswish@microsoft.com. For reference the support person that
> gave
> me the responce that there would be no hotfix is Martin Ma
>
> "Manuel Lopez" wrote:
>
>> That's strange. How can there not be a hotfix if it breaks networking on
>> so
>> many computers and all versions of windows (however, one poster says only
>> amd machines are affected--I haven't tested with intel)? I would expect
>> there to be a lot of complaints from customers, corporate and otherwise,
>> once they realize the problem (and the cause).
>>
>> Let me know where you submitted your query/complaint on this, and I'll
>> send
>> another.
>>
>>
>> "Jeffrey" <Jeffrey@discussions.microsoft.com> wrote in message
>> news:579D3D8F-B7DD-46C5-B430-19C2947EF707@microsoft.com...
>> > Here is part of the reply Microsoft provided:
>> >
>> > "I fully understand the inconvenience of this issue. However, I am
>> > afraid
>> > that there will not be a hotfix for this issue. "
>> >
>> > I suggest sending as many messages as possible in complaint over this
>> > as
>> > they have effectivly made network drives useless with no intention to
>> > correct
>> > the problem.
>> >
>> > "Manuel Lopez" wrote:
>> >
>> >> Good, with so many affected and such a severe bug, it should get fixed
>> >> quickly (--right?).
>> >>
>> >> Folders and files have all reappeared on one computer and disappeared
>> >> from
>> >> another, but I haven't the slightest idea why (perhaps related to
>> >> which
>> >> peer
>> >> gets chosen as "browsing master" or when). Anyway, thanks for filing
>> >> the
>> >> MS
>> >> report.
>> >>
>> >>
>> >> "Jeffrey" <Jeffrey@discussions.microsoft.com> wrote in message
>> >> news:16D78841-2A44-4538-B480-7C5AF313C90F@microsoft.com...
>> >> > This problem is not limited to peer-to-peer networks but all network
>> >> > shares.
>> >> > Server-client based networks have the same problem with a seemingly
>> >> > random
>> >> > folders and files not showing up on network drives. There were
>> >> > updates
>> >> > for
>> >> > Windows 2000 at the same time, but W2K stations have no problems
>> >> > reading
>> >> > network files correctly only XP stations. I have not seen a KB
>> >> > writeup
>> >> > but
>> >> > I
>> >> > have send in a feedback to MS regarding this problem so hopefully
>> >> > they
>> >> > will
>> >> > get on it quickly. One odd thing I found also, if you copy a folder
>> >> > on
>> >> > the
>> >> > local system the copy will show up remotely, but if you delete the
>> >> > origional
>> >> > after that and rename the copy it is again invisible.
>> >> >
>> >> > "Manuel Lopez" wrote:
>> >> >
>> >> >> Thanks, at least it's good that this is a known problem (as opposed
>> >> >> to
>> >> >> having to prove there's a problem and then get someone to notice).
>> >> >> Any
>> >> >> KB
>> >> >> article or bulleting on this bug yet?
>> >> >> I have to add, it's very strange behavior: arbitrary files and
>> >> >> folders
>> >> >> will simply become invisible, but then sometimes reappear. The
>> >> >> only
>> >> >> consistent thing (so far) is that if files become invisible, all of
>> >> >> the
>> >> >> files in a given folder become invisible, not just some.
>> >> >> It seems like a major thing to slip through testing, but then
>> >> >> one
>> >> >> might
>> >> >> not notice because it seems to be only a few out of many folders
>> >> >> are
>> >> >> affected. (--they're also probably not very enthusiastic about
>> >> >> peer-to-peer
>> >> >> networks).
>> >> >>
>> >> >>
>> >> >> "Jeffrey" <Jeffrey@discussions.microsoft.com> wrote in message
>> >> >> news:434B20BE-839E-4128-A393-B51A59508C8B@microsoft.com...
>> >> >> > Yes, this is a problem caused by the Feb 8th security updates. It
>> >> >> > affects
>> >> >> > both Professional and Home editions of Windows XP. The only
>> >> >> > workaround
>> >> >> > is
>> >> >> > to
>> >> >> > remove these updates until Microsoft gets around to correcting
>> >> >> > the
>> >> >> > problem
>> >> >> > their latest update has caused. This is a major problem for
>> >> >> > business
>> >> >> > clients
>> >> >> > who use a network for their company.
>> >> >> >
>> >> >> > "Manuel Lopez" wrote:
>> >> >> >
>> >> >> >> After installing the package of 9 or 10 security updates
>> >> >> >> released
>> >> >> >> by
>> >> >> >> Microsoft on February 8th, the following problem began:
>> >> >> >> Some network folders show no files in windows explorer or
>> >> >> >> command
>> >> >> >> prompt, but the files are there; for example, copying from
>> >> >> >> another
>> >> >> >> folder
>> >> >> >> to
>> >> >> >> the supposedly empty folder generates a "overwrite" warning in
>> >> >> >> explorer.
>> >> >> >> The problem only occurs in some folders and not others, with no
>> >> >> >> apparent
>> >> >> >> rhyme or reason to it.
>> >> >> >>
>> >> >> >> These are networked XP Pro computers with sp 2 installed, in a
>> >> >> >> workgroup
>> >> >> >> (peer-to-peer), using tcp/ip with simple file sharing turned
>> >> >> >> off.
>> >> >> >> They
>> >> >> >> had
>> >> >> >> no problems prior to the patch, and I tracked down the problem
>> >> >> >> as
>> >> >> >> beginning
>> >> >> >> immediately after installation of this group of patches.
>> >> >> >>
>> >> >> >> Can anyone confirm problems caused by these updates?
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>
Facebook
Twitter
Instagram