Login to Account Create an Account
re: kb885835 & kb885250
Posted 13 February 2005 - 08:28 AM
But i prefer this method. It s easier to maintain than integrating all hotfixes (with nlite for ex.)
Posted 13 February 2005 - 12:17 PM
Thank you for contacting Microsoft Online Support. My name is Xxxxxx, and I am an Escalation Engineer for the Windows Support Team. In order to better serve you and resolve this issue more efficiently, I have taken ownership of your Service Request. I appreciate the time and effort you have taken on this service request.
Going forward, I will be working with you to address the issue as soon as possible. To contact me, you may directly send emails to my account: firstname.lastname@example.org with the case ID SRZxxxxxxxxxxx.
As I understand, Windows Update 885250 cannot be integrated to a folder after Windows Update 885835 is integrated to that folder.
I would like to explain that neither 885250 nor 885835 is a beta update. Microsoft keeps release Windows Update to improve the security of the systems. Xxxxxx means that Microsoft will still release updates to update the files updated by 885250 if a potential problem is found in the files. The updates are fully tested before they are released.
To provide you with the most accurate support, please let me know the error message appears when you try to use the \integrate switch to integrate the update to the folder.
Please capture a screenshot when the issue happens:
1) Press the Print Screen key (PrtScn) on your keyboard.
2) Click Start, click Run, type MSPAINT, and click OK.
3) In Paint, click Paste under the Edit menu, click Save under the File menu, type a file name for the snap shot, choose JPEG as "Save as type", and click Save.
4) Please send this file to the email account: email@example.com
Please try the suggestions above on your side and provide me with the results at your earliest convenience. If anything in my e-mail is unclear or you need further help, don't hesitate to let me know. It is my pleasure to be of assistance.
I am looking forward to your reply.
I have just finish taking his snapshots, I did one whith 885835 first and another with 885250 first, the exact same error, but just for his reference. I actually installed the hotfixes in different orders, one numerically the other but release date.
Will post any response.
Posted 16 February 2005 - 02:42 PM
Posted 16 February 2005 - 02:51 PM
Posted 16 February 2005 - 03:39 PM
Posted 16 February 2005 - 04:05 PM
So ... the method I use seems to still be described HERE, called The Combination Installation. Note it is also desribed on the document I linked to in my previous post, just pretend the desired hotfix has an older UPDATE.EXE
If you want to integrate software updates that use Update.exe versions earlier than 188.8.131.52, follow steps 6 through 13 to integrate these updates.
Hope that clears things up ...
Posted 16 February 2005 - 04:20 PM
Be careful with the KB885250 one it's bad for some networking types.
Posted 18 February 2005 - 09:28 AM
If you are using this method, KB885835 must be integrated before KB885250, otherwise you will end up with Mrxsmb.sys version 5.1.2600.2541 and effectively the issues addressed by KB885250 will not be fixed.
Also it is not necessary to copy out any files from /svcpacks/ merely open up HFINT.DAT after integrating KB885835 and change the filename mrxsmb.sys to something else before integrating KB885250, then change it back to its original name after integrating KB885250 as the following example shows:
In HFINT.DAT change:[KB885835] mrxsmb.sys lsasrv.dll rdbss.systo:[KB885835] mrxsmb.sys.tmp lsasrv.dll rdbss.sysIntegrate KB885250.
Then change:[KB885835] mrxsmb.sys.tmp lsasrv.dll rdbss.sysback to:[KB885835] mrxsmb.sys lsasrv.dll rdbss.sys
This type of workaround should work, however it would be nice if Microsoft would address the issue properly.
In HFINT.DAT change:
[KB885835] mrxsmb.sys lsasrv.dll rdbss.systo:
[KB885835] lsasrv.dll rdbss.sysIntegrate KB885250.
That's all . Beter or no?
Posted 18 February 2005 - 09:34 AM
Posted 18 February 2005 - 11:22 AM
Posted 18 February 2005 - 11:37 AM
And in the continuing saga I rcvd this from M$ today (NOTE: IT DOES NTO WORK, just posting to keep everyone informed. I have sent them the current working method along with the proof that their way does not work and mine does.)
Thank you for the reply.
I apologize for the delay. I tested the issue on several of my machines and reproduced this issue.
This issue can occur because some files are duplicated in the updates and the version is the same. I have reported this issue to our Windows Update team for their immediate attention.
Meanwhile, I would like to suggest you use the following method to workaround this issue:
I suggest either integrate 885835 and the other updates before 885835, and then, please use the following method to workaround this issue:
1. Download 885250 again from the following link to the hard drive.
2. Use the /X switch to extract the files to a folder.
3. You will see several folders in this folder:
Please copy the sys file in SP2QFE along with the spcustom.dll file in the update folder, and the file spmsg.dll to the i386 folder that contains the integrated files.
After copying these 3 files to the i386 folder, the update 885250 has been integrated to the folder.
Please let me know the results at your earliest convenience. If anything above is unclear, please don't hesitate to let me know and I will be glad to be assistance.
You still do not end up with kb885250 installed, I'd post the screen shots, but whats the point.
Posted 22 February 2005 - 07:24 AM
Here's their ?final? response:
Thank you for the reply and letting me know how you resolved the issue.
The method you used is one of the workarounds available now.
I am glad that the updates are integrated successfully. I really appreciate your time and effort on this issue.
I will keep you updated if there is any update from the Windows Update team about if they will change the registry part of the INF file.
Please understand that our support team handles system malfunction issues. However, to resolve this issue completely, we need to change the installation package of the updates. I will forward the information to you if I get any update from the development team.
Although, we are not able to resolve the problem without using a workaround, we still want to let you know that we always strive to provide high level support to our customers and hope you are happy with the whole process so far with this service request. If there is anything you are not very satis
fied with, please don't hesitate to let us know as your feedback is very valuable and meaningful to help us improve our service process and quality. Our goal is to provide 1st class customer service to our customers.
If you agree, I will mark our case as temporary closed before there is any update from the development team.
Please let me know if you have you any further concerns on this issue.
I look forward to hearing from you.
For those who didn't follow the entire thread here the "workaround" mentioned is in the first post of this thread.
Posted 22 February 2005 - 11:35 AM
Posted 22 February 2005 - 11:49 AM
Actually I take that back I do have a driver problem with an ATI product but I won't call Microsoft about that.
Posted 22 February 2005 - 12:06 PM
Posted 22 February 2005 - 12:08 PM
Posted 22 February 2005 - 06:30 PM
Works the best and it takes ~10 sec - Move it on 1st page!
The method described now on 1st page is
Posted 22 February 2005 - 07:53 PM
sysmain.sdb is common, and there is no teling which one is newer (unlike dll no version number.
Probably the one from KB886716 (since the fix is from february and the other one from 2004)
Posted 22 February 2005 - 10:42 PM
I have changed the first post to note that only the line in HFINT.DAT needs to be modified. by adding anything to the end of mrxsmb.sys after integrating kb885835.
Posted 25 February 2005 - 07:58 PM
for your use change line 2 from
to point to your cd working directory.
Leave Service pack 2 with its full name or change line 5 to point to what you named it. (Don't have it name KB835935.exe or it will try to integrate twice.)
rename the other hotfixes to KBxxxxxx.exe.
have the hotfixes in the same directory as this script and away you go. Takes less than 2 minutes on my system. SP2 and 17 hotfixes.
@echo off set sourcedir=h:\bootcd\working set svcpackdir=%sourcedir%\i386\svcpack echo Integrating Sevice Pack 2 if not exist %sourcedir%\win51ip.sp2 start /wait WindowsXP-KB835935-SP2-ENU.exe /integrate:%sourcedir% /q echo integrating KB885835.exe start /wait KB885835 /integrate:%sourcedir% /q for /f %%L in (%svcpackdir%\HFINT.DAT) DO ( if %%L==mrxsmb.sys ( echo %%L.temp>>%svcpackdir%\HFINT.TMP ) ELSE ( echo %%L>>%svcpackdir%\HFINT.TMP ) ) move /y %svcpackdir%\HFINT.TMP %svcpackdir%\HFINT.DAT for %%U in (KB??????.exe) DO ( if not exist %svcpackdir%\%%U ( echo integrating %%U start /wait %%U /integrate:%sourcedir% /q ) ) for /f %%L in (%svcpackdir%\HFINT.DAT) DO ( if %%L==mrxsmb.sys.temp ( echo mrxsmb.sys>>%svcpackdir%\HFINT.TMP ) ELSE ( echo %%L>>%svcpackdir%\HFINT.TMP ) ) move /y %svcpackdir%\HFINT.TMP %svcpackdir%\HFINT.DAT Echo FINISHED pause
Posted 26 February 2005 - 09:09 AM
Thank you for the reply.
I do appreciate your time reporting further solutions to us.
I also found some similar solutions on some forums:
I have forwarded the information to our Windows Update development team.
Once again, I would like to thank you for brining this issue in to our attention. Your time and effort on this matter is appreciated.
We do appreciate having users like you who stand closely with our products and always provide such great feedback. It is your efforts help to make our product powerful and easy to use.
If I get any update from the development team, I will surely let you know as soon as possible.
Thank you for choosing Microsoft and taking time to let us know the problem as well as the further information!
Posted 26 February 2005 - 09:16 AM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users