Glenn9999
Content Type
Profiles
Forums
Events
Posts posted by Glenn9999
-
-
(1) 890830, (2) 928366, (3) Root Certificates Update, (4) 928416, (5) 914440 & (6) 829019
can any one kindly tell me how to integrate these updates into my xp unattended cd
1. 890830 is Microsoft's Malicious Software Scanner. It gets updated and presented every month, and is considered updated when the latest version is run. This is not really a patch.
2. 928366 is the latest .NET 1.1 security update. I don't know much about its integration, but I do a lot of people are having issues with some of Microsoft's latest security update. Read http://support.microsoft.com/kb/928366
3. This one is updated periodically, and I'm not sure there's an integration option on it (it uses the old wextract patching tech from 98/ME if I recall correctly).
4. 928416 isn't specifically a patch. I think though it might refer to one of the releases of the .NET framework (3.0 maybe?) . http://support.microsoft.com/kb/928416
5. 914440 is the Network Diagnostics Tool. You might have a newer version offered to you than what you have. Or it might have issues with integration as an application more than a patch. http://support.microsoft.com/kb/914440
6. 829019 is another pointer to a .NET install (2.0 maybe?) http://support.microsoft.com/kb/829019
Hope that helps you get into the right direction.
0 -
I'm missing the switch to disable the system restore. do you know it? i couldn't find it anywhere!
There isn't one, because system restore has nothing to do with the patches. You have to do it separately yourself. Microsoft doesn't recommend that you forcibly disable system restore, either.
It looks like, though, you can use the DisableSR key with this registry path:
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\SystemRestore
I notice it runs as a service, too, so perhaps you can disable that through registry or API call for while you are running your script (I guess that's the question? Maybe it might be beneficial to tell us what you're looking to do specifically.
I will note there is also an API service that will clear system restore points.
0 -
I just got three files today through Windows Update for Windows XP SP2.
928365 and 928366 are updates for .NET 1.1 and .NET 2.0. You can get the appropriate update for what you're running here:
http://www.microsoft.com/technet/security/...n/ms07-040.mspx
Then of course, 890830 shows up every month.
http://www.microsoft.com/downloads/details...;displaylang=en
0 -
@Glenn: You hit everything on the nose. However, 2 of your IE7 patches are replaced. KB928090 is the cumulative update from February and KB931768 is the one from May. Both are replaced by KB933566.
I double-checked and agree with you about KB931768. However, KB928090 is required, as Microsoft made a big error in not including a file in the IE7 package in subsequent packages for it to be considered as "completely replaced".
corpol.dll is in:
KB928090-IE7 7.0.6000.16414
KB928090-IE7 7.0.6000.16414 7.00.6000.16414
(the first column is the update version and the second is the version of the file in the system (in this case windows/system32)
See
http://www.neowin.net/forum/lofiversion/in...hp/t559309.html
and also the post of: Thursday, May 10, 2007 12:52 AM by Michael Kraft at http://blogs.msdn.com/ie/archive/2007/05/0...w.aspx#comments
I find no indication that this file was rendered non-relevant, though I notice that Microsoft went and took out corpol.dll from 928090. Is the file rendered useless?
Of course, there are certain files only updated in the IE6 packages that seem to get used in IE7 (browseui.dll and shdocvw.dll) which still seem to be available to the end user (they're in windows/system32 after an upgrade to IE7). It'd be nice to get some answers, or at least some consistency. Right now it seems it's required for one to uninstall IE7 entirely and then update IE6 and then reinstall IE7 & updates to be fully updated. Silly, but seems true.
0 -
Usually the IE6/IE7 patches are just folded into the pile as XP patches. I usually try to mark them separately to indicate what they are. Here's the list of what I have.
IE6-WindowsXP-KB929969-x86-ENU.exe
IE6-WindowsXP-KB933566-x86-ENU.exe
IE7-WindowsXP-KB928090-x86-enu.exe
IE7-WindowsXP-KB929969-x86-enu.exe
IE7-WindowsXP-KB931768-x86-enu.exe
IE7-WindowsXP-KB933566-x86-ENU.exe
when I see in changes that some updates were removed, does that mean they no longer are of any use or are included in some new ones?Usually if you see an update removed out of a list, it's recognized that the update is old. Or, a newer patch includes the changes in the older patch.
Will it create any problems if I just keep adding the new ones and keep the old ones still?No.
0 -
For those that are interested, I got offered this through Windows Update:
06/27/2007 Update for .NET Framework 3.0: x86 (KB932471)
Evidently, they haven't updated their regular support page to have this download. This link will get the file for you.
I also saw a new Root certificate update file.
0 -
Anyone know of one?
0 -
Another question I had. What's the difference between what is done in the registry tweaks here (tweaks_en.reg)
; Adds "Command Promtp Here" to right click context menu
[HKEY_CLASSES_ROOT\Directory\shell\Command Prompt Here]
@="Command Prompt Here"
[HKEY_CLASSES_ROOT\Directory\shell\Command Prompt Here\command]
@="cmd.exe /k cd %1"compared to the "Open Command Window Here" Powertoy" that Microsoft offers? Do they do basically the same thing or is there more to what Microsoft is doing that they put out a 514KB file to do this job?
Edit: Partial answer, I looked at the Powertoy a bit closer, it does basically the same thing as above but adds a bunch of other registry entries along with CMDHERE.DLL in the System32 folder. Question now is does CMDHERE.DLL provide any functionality?
0 -
I rather like this tool much better.
http://www.msfn.org/board/index.php?showto...mode=linearplus
0 -
I thought I'd mention a slight "problem" I encountered (I'm sure a false-positive) more for awareness sake than anything, since I don't see it already mentioned. When I ran AVG Anti-spyware (Ewido) against my computer, security.reg in this package was identified as "Trojan.Disabler.c". Hard telling for me to know what it's finding, but thought it might be interesting for someone to be aware of it.
0 -
I don't know if the original poster of this one is reading or not but the thing I just finished (Batch Patcher) might fit for what you're wanting. Point it to the directory you have your fixes in and set it to run them. Then it should run all of them for you, then give you a prompt to reboot. There's an unattended mode, too, so you should be able to just run a single command to apply all the patches to your system that you have (minus a few).
0 -
I see an attachment facility so I'll put it on this thread too.
Edit: All links removed from all posts except the attachment facility link.
0 -
Good bet.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates
You'll find for each patch (most of them anyway) applied to the system that it will list the files in the patch along with versions and where on the system the file was placed. If you put all the values in that subkey path together in the right way it can tell you a file version history along with the patch ID for each one. It doesn't give you anything certain, but it points you towards some places to look.
A good example of something that came out of the registry on my computer after I put the data together:
tzchange.exe is in:
KB928388 5.1.2600.3037 5.1.2600.3073
KB929120 5.1.2600.3042 5.1.2600.3073
KB931836 5.1.2600.3073 5.1.2600.3073
The current version of the file on the machine is 5.1.2600.3073 (that's the third column), so you can look at the other two patches as possibly deprecated by KB931836. Now Microsoft sometimes patches a file along with other things, so you really do have to check things out. But it's a better start than just looking up all the KB numbers.
BTW, if you look at the KB entry for 931836 it says: "The update that this article describes is a cumulative update rollup that includes all the changes that were previously released in Microsoft Knowledge Base articles 928388 and 929120." So those two patches are safe to delete.
0 -
As it turns out, I found out that Microsoft put all I wanted to know about this topic in the registry, so I have all I want to know
0 -
So maybe the M$ documentation refers to the WinXP System Restore. [?]
Nope. Refers to WinME, WinXP, and Vista. Could be that they were mistaken? Don't know for sure.
0 -
The question I have is how do you determine which patches are still valid? In other words, say a patch comes out that patches the same files as another patch did in the past. Is there a quick way to find that out by looking at the patch files? Or do you have to read all the KB entries and see if it mentions newer versions of the same files?
0 -
I was looking at some documentation for System Restore on the Microsoft site and was trying to program something for Windows ME, but didn't find the DLL I was using (SRCLIENT.DLL) on the system anywhere. Does anyone know what general package this comes in (an option maybe that wasn't selected on install, or a downloadable package?), or if the documentation might be misleading me and SRCLIENT.DLL shouldn't exist on Windows ME?
0 -
I wrote a program that I've been using on Windows ME and XP to apply a number of patches at once to the system.
The basic idea of how it works: There's an interactive mode and non-interactive mode. Select the patches (or provide the directory on the command line) and then it runs the patches then offers to reboot. More details are in the text file with the program.
Comments or questions welcome in this thread.0
HOTFIXES: Win2000 SP4, WinXP SP2, WinXP SP3 and Win2003 SP2
in Unattended Windows 2000/XP/2003
Posted
FWIW, I got offered on Windows Update in addition to what was listed.
933579 - msxml6
936181 - msxml4 connected to 933579
Both are related to the 936021 patch already listed. (security patches for the same issue)
And I can't get a download page/link for 937143, the page Microsoft has linked is not available.