Sign in with
Sign up | Sign in
Your question

xp Feb 8 update package: Invisible files in some network f..

Tags:
  • Security
  • Microsoft
  • Windows XP
Last response: in Windows XP
Share
Anonymous
a b 8 Security
February 13, 2005 6:05:14 AM

Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.network_web,microsoft.public.windowsxp.security_admin (More info?)

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?

More about : feb update package invisible files network

February 13, 2005 12:01:02 PM

Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.network_web,microsoft.public.windowsxp.security_admin (More info?)

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?
>
>
>
Anonymous
a b 8 Security
February 13, 2005 3:21:03 PM

Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.network_web,microsoft.public.windowsxp.security_admin (More info?)

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?
>>
>>
>>
Related resources
February 13, 2005 3:21:04 PM

Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.network_web,microsoft.public.windowsxp.security_admin (More info?)

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?
> >>
> >>
> >>
>
>
>
Anonymous
a b 8 Security
February 13, 2005 9:05:50 PM

Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.network_web,microsoft.public.windowsxp.security_admin (More info?)

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?
>> >>
>> >>
>> >>
>>
>>
>>
February 23, 2005 10:57:04 AM

Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.network_web,microsoft.public.windowsxp.security_admin (More info?)

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?
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>
Anonymous
a b 8 Security
February 25, 2005 2:43:55 AM

Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.network_web,microsoft.public.windowsxp.security_admin (More info?)

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?
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>
February 25, 2005 10:55:03 AM

Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.network_web,microsoft.public.windowsxp.security_admin (More info?)

I places an email support request for Windows XP SP2 at
http://support.microsoft.com/oas/default.aspx?&c1=509&g...
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?
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>
Anonymous
a b 8 Security
February 25, 2005 2:00:38 PM

Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.network_web,microsoft.public.windowsxp.security_admin (More info?)

Thanks, I'll report it to ms at those websites as a critical/severe bug:
kb885250 arbitrarily prevents access to some but not all shared folders on
properly configured windows xp sp2 and other windows networks, both
peer-to-peer and client/server.

(It may be that only people using netbios, i.e. non-dns style, names are
seeing it, but that still makes it a widespread problem. Despite what that
rep said, I assume they'll withdraw or fix kb885250 over the next few weeks
as the complaints increase and the cause is tracked down.)

"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&g...
> 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?
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>
Anonymous
a b 8 Security
February 26, 2005 2:02:53 PM

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&g...
> 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?
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>
March 1, 2005 10:35:09 AM

Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.network_web,microsoft.public.windowsxp.security_admin (More info?)

I got a useful reply back after elevating the problem to a support manager,
this time is was quite different then the first responce:
"Going forward, I will be working with you to bring this issue to a
resolution as soon as possible. I understand the problem to be:

After installing security updates, some files and folders on networked drive
do not showing up on remote systems no longer.

If I am not accurate in my understanding of this case, please feel free to
correct me.

I understand that you have invested much time and effort in this case. I
appreciate your cooperation and apologize for any inconvenience. Please be
assured that I will try everything I can to assist you and resolve the issue
as soon as possible.

Regarding the current status about the update 885250, I have reported this
issue to my manager and our related team. We will try our best to work out a
solution to this is issue.

Once there is any update or hotfix about this issue, I will let you know as
soon as possible.

Please let me know if this addresses your concerns. If anything is unclear
in my email, please don't hesitate to let me know and I will be glad to help.

I look forward to hearing from you.

Best Regards,

Peter Gao"
Anonymous
a b 8 Security
March 1, 2005 2:18:03 PM

Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.network_web,microsoft.public.windowsxp.security_admin (More info?)

This was my reply from a regular support rep:

"I have reported this issue and the detailed information to our Develop
Group. They put emphasis on the information you have provided and I believe
an update patch will be released soon in the future. Please also be assured
once there's a solution to this problem be found on our side, I will notify
you as soon as possible."



"Jeffrey" <Jeffrey@discussions.microsoft.com> wrote in message
news:512A8C8D-50AE-4A0E-A0BD-A379DEB8B380@microsoft.com...
>I got a useful reply back after elevating the problem to a support manager,
> this time is was quite different then the first responce:
> "Going forward, I will be working with you to bring this issue to a
> resolution as soon as possible. I understand the problem to be:
>
> After installing security updates, some files and folders on networked
> drive
> do not showing up on remote systems no longer.
>
> If I am not accurate in my understanding of this case, please feel free to
> correct me.
>
> I understand that you have invested much time and effort in this case. I
> appreciate your cooperation and apologize for any inconvenience. Please be
> assured that I will try everything I can to assist you and resolve the
> issue
> as soon as possible.
>
> Regarding the current status about the update 885250, I have reported this
> issue to my manager and our related team. We will try our best to work out
> a
> solution to this is issue.
>
> Once there is any update or hotfix about this issue, I will let you know
> as
> soon as possible.
>
> Please let me know if this addresses your concerns. If anything is unclear
> in my email, please don't hesitate to let me know and I will be glad to
> help.
>
> I look forward to hearing from you.
>
> Best Regards,
>
> Peter Gao"
>
!