KB885250 Problem

G

Guest

KB885250 is causing problems when files or applications are shared from
Windows 95/98/Me machines. In the case of our DOS multi-user database
application, if the application and data reside on a 95/98/Me machine, a user
on XP that has this security update installed is not allowed to create any
files from the application on the host machine.

This is a major problem, and the only solution I have at this point is to
have users uninstall this update.

Is anyone aware of a way to install the update and change something that
will allow shared files and applications on 95/98/Me machines to function
properly?

Thanks
 
M

Malke

Outrage said:
KB885250 is causing problems when files or applications are shared
from Windows 95/98/Me machines. In the case of our DOS multi-user
database application, if the application and data reside on a 95/98/Me
machine, a user on XP that has this security update installed is not
allowed to create any files from the application on the host machine.

This is a major problem, and the only solution I have at this point is
to have users uninstall this update.

Is anyone aware of a way to install the update and change something
that will allow shared files and applications on 95/98/Me machines to
function properly?

Thanks

Here's information I found provided by another MVP:

KB885250, an update from 2/8/2005 can cause file and printer sharing
problems under Windows networking and SAMBA.

XP SP2 clients seem unaffected, the issue surfacing for XP SP1 clients
with this hotfix applied. If your attempt to use SMB shares seems
compromised after last week's hotfixes, remove KB885250.

See this MS Knowledge Base article:

http://www.microsoft.com/technet/security/bulletin/ms05-011.mspx

Check in the section "Vulnerability Details, Workarounds" for several
approaches to providing the protection of the hotfix without using the
hotfix.

Malke
 
M

Manuel Lopez

No, xp sp2 is ALSO affected by serious networking problems if 885250 is
installed; the files in random folders become inaccessible, among other
issues--and this is true even on networks consisting only of windows xp sp2
machines.
 
M

Malke

Manuel said:
No, xp sp2 is ALSO affected by serious networking problems if 885250
is installed; the files in random folders become inaccessible, among
other issues--and this is true even on networks consisting only of
windows xp sp2 machines.
Thanks, Manuel. I'll change my notes accordingly. I have to go on what
others have reported since I haven't had any problems with that update
personally on any of the XP boxen (all SP2) and haven't had any
problems with interoperability with Samba on the Linux boxen.

I appreciate the update.

Malke
 
G

Guest

I had other issues in my work environment. My Windows 2000 Professional SP3
admin workstation BSOD'ed after applying the latest round of security
updates. Looking at the updated file lists I suspect that the KB885250 was
the culprit. Replacing .SYS files means potentially affecting the boot
environment. I couldn't get my workstation into Windows by using any of the
Safe Modes or using the Last Known Good Configuration option. Had to wipe it
out and reinstall from scratch.

Looks like this KB885250 update might be *almost* as catastrophic as the
infamous Windows NT 4.0 SP6, which broke TCP/IP. Hence the rush release of
SP6a. Glad that I tested the 2/2005 updates on my own workstation before
rolling them out companywide!
 
T

Tami

Yes! I have also experienced this problem (search this NG for other 885250
posts).

The strange this is, I've only experienced this on AMD machines. I applied
the update to all my XP-2 machines at work (Intel), and everything was fun.
But at home, all machines are AMD, and the randomly (but consistent)
dissappearing files problem is at hand...
 
B

bushy

We have a P2P network using a Win 98 machine to store files
From our XP SP2 workstations we cannot 'save as' using a new filenam
on the Win 98 share with KB885250 installed

I spent a couple of hours trying to find the problem on the firs
workstation to be affected when the user told me she had clicked th
Update icon before going to lunch, the problem appeared after lunch
Ten updates had been installed on this machine on the day.
uninstalled them all and re-installed one at a time to find th
culprit
 
M

Manuel Lopez

Unfortunately, apparently MS won't fix this, at least according to one rep.
See this post from another thread:

Jeffrey said:
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.

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.
 
G

Guest

Copied this from a post I made on another forum, but it explains how to make
sure that an update, KB885250 in particular, doesn't install

Check for Hotfix KB885250 on the Client -
go to Control Panel/Add & Remove Programmes, check the Show Updates box at
the top of the window. The updates are listed at the bottom; scroll down to
find them.

If KB885250 is present remove it. You may get a message saying other
programmes may not work, ignore it. When you have removed the hotfix try
accessing your host. With older versions of Windows on the Host it seems that
you cannot carry out a 'Save As' command with a changed file name but there
are other symptons with other OSs.

If this works go to Windows Update select Custom Install and scan for
updates. KB885250 should be on the list of critical updates. Uncheck the
Install box and check the 'Hide this Update' box.
Also watch out for the Windows Security icon appearing in the task tray. If
it does click on it select Custom Install, deselect KB885250 and click
Install or Close. A dialogue will open 'Do not remind me about this Update',
Check the box.
Finally Updates sometimes install on shutdown, a notice will appear on the
Shut Down dialogue, click on 'Do not install updates' Next time you switch on
the Security Icon should appear and you can follow the procedure above to
prevent 885250 installing.
Once you have told it not to 'remind me' it shouldn't install.
 
M

Manuel Lopez

please note this post from the other thread on where to report this bug:

Jeffrey said:
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 (e-mail address removed). For reference the support person that
gave
me the responce that there would be no hotfix is Martin Ma

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.)
 
M

Manuel Lopez

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]
 
T

Tami

In my case, I first noticed this because I bought a new computer, and was
transferring my logs from my old computer to the new one (fresh install of
XP-2 slipstream + recent updates that include the dreaded 885250)

Here is an example of an "invisible" filename:

\\olympia\c$\Documents and Settings\shenan.INTROVERTED\My Documents\Logs\ICQ
\Chats\Chats.rar

Other files in that folder do appear, but not that particular one. I CAN
however manually type in the complete filename to get to the file, it just
does not show up in explorer (nor does it copy over when copying from the
root folder which contains it)... :-(
 
M

Matt

I have experienced issues with this update too and have uninstalled it
from company XP machines. I'm applying anything relevant from the
vulnerability workarounds until (if?) it is addressed by Microsoft.

However, my circumstances are different in that we run an Appleshare
6.3 server (SMB based) which ceased being browsable, even though
authentication seemingly takes place normally.

Also, I was still able to access my SMB shares as usual on our Debian
Linux servers (smbd 2.2.3a-14.1) with KB885250 installed so I imagine
the Linux/Unix interoperability issues are fairly build/distro
specific.
 
D

daboysjason

Matt said:
I have experienced issues with this update too and have
uninstalled it
from company XP machines. I'm applying anything relevant from
the
vulnerability workarounds until (if?) it is addressed by
Microsoft.

However, my circumstances are different in that we run an
Appleshare
6.3 server (SMB based) which ceased being browsable, even
though
authentication seemingly takes place normally.

Also, I was still able to access my SMB shares as usual on our
Debian
Linux servers (smbd 2.2.3a-14.1) with KB885250 installed so I
imagine
the Linux/Unix interoperability issues are fairly build/distro
specific.

I operate and maintain a couple of local area networks and we have
been having this problem. After researching I had also come accross
this issue of KB885250 update. After uninstalling this update all
computers accorss the network were able to once again browse all
files.

Why Microsoft will not fix this I’m not sure, but I think everyone
should file a formal complaint as this is un-acceptable to anyone
using a computer network.


Thanks
Jason
 
J

John

Thanks Bushy, that's how I tracked it down too (but not that quickly!)
The problem is that one of the computers I messed with now has the
kb885250 installed, but because I ran "System Restore" while
experimenting, the kb885250 doesn't show up in the add/remove list. So
now I'm trapped with the update installed and messing up the file
saving, but no obvious way to uninstall it. What a mess!


I had this same problem as a result of deleting the
C:\Windows\$NtUninstallKB885250$ directory. I could neither uninstall
it or reinstall it and then uninstall it.

However, I have another pc with the same OS - XP+SP2 - and file
structure on which I hadnt deleted the
C:\Windows\$NtUninstallKB885250$ directory so simply copied the whole
directory across and uninstalled it using spuninst.exe which is in
that directory's tree.

This worked (fingers were tightly crossed) and 885250 successfully
removed.

John


X-Signature: Effluent

***IMPORTANT***
Please do not reply to (e-mail address removed)
This is an antispam address.
Please replace effluent with archway.
..
 
N

Neal

Gary,

Thanks so much for your post. I spent hours with Microsoft both on the
phone and in repeated emails just trying to get them to acknowledge the
problem.

FYI, the issue with KB885250 also affects Snap Servers since they use
the same method of SMB. Snap's (Adaptec's) response was totally
unacceptable (asking users to buy a $699 OS upgrade per server!)

http://adaptec-tic.adaptec.com/cgi-...3J0PSZwX3Jvd19jbnQ9NDM0MyZwX3BhZ2U9MQ**&p_li=

Great to see this issue will finally be fixed by Microsoft. I imagine
KB895900 will undergo more testing and then finally replace the
defective KB885250.

Again, thanks for helping the user community by posting this
information.
 
G

Guest

Hello Manuel Lopez,

I have been fighting this problem for several of my clients, I found a
hotfix that did not work, I still have the problem and I have also tested
this from a CMD prompt and here is my results.

When I isssue a "Dir" command by itself it reports no files or folders.

if I issue a "dir *.exe" I can see all the executables.

I have opened a ticket with MS and when they resolve the issue I will update
this post.

Garyp

==============================================

Z:\2003 Resource Kit>dir
Volume in drive Z has no label.
Volume Serial Number is AAAA-AAAA

Directory of Z:\2003 Resource Kit

File Not Found

Z:\2003 Resource Kit>dir *.exe
Volume in drive Z has no label.
Volume Serial Number is AAAA-AAAA

Directory of Z:\2003 Resource Kit

03/22/2005 07:13 AM 12,337,752 en_windows_server_2003_reskit.exe
03/30/2005 02:35 PM 392,552 q329357_WXP_SP1_x86_ENU.exe
03/30/2005 11:46 AM 12,337,752 rktools.exe
03/18/2005 08:55 AM 4,934,480 WindowsXP-KB838079-SupportTools-ENU.exe
4 File(s) 30,002,536 bytes
0 Dir(s) 49,053,638,656 bytes free

Z:\2003 Resource Kit>
 
M

Manuel Lopez

Thanks for your note. I'm waiting for xp sp3 to fix the problem (I assume
it will be fixed by then), and have removed kb 885250 from my systems and
also hidden it from appearing on windows update.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top