richardf Posted December 30, 2007 Report Share Posted December 30, 2007 Somebody could it say to me if : There exists a means of knowing if a hotfix for Vista applies with the SP1 already installed? My best wishes for all. Richard Quote Link to comment Share on other sites More sharing options...
terroradagio Posted January 3, 2008 Report Share Posted January 3, 2008 I would think Vista would tell you. When you go to install a hotfix, it will detect if you need it or not pre or post SP1. Quote Link to comment Share on other sites More sharing options...
xable Posted January 3, 2008 Report Share Posted January 3, 2008 Yep that`s true for all versions of windows terroradagio, in vista the message you get is, this update doesn`t apply to your system, or something along those lines. Quote Link to comment Share on other sites More sharing options...
richardf Posted January 4, 2008 Author Report Share Posted January 4, 2008 Hello, Thank you with you two for the answer (answer which I had intellectually anticipated). But that implies at least two things: 1) Obligation systematically to launch the installation of an unspecified hotfix to know if VISTA decided to apply it 2) In corollary, in other words, it is necessary to make an absolute confidence with VISTA However, the recent experiments showed me that VISTA could fail in the detection of opportunity of applying or not a corrective measure. For example: - You launch a hotfix already installed; VISTA will answer “this update doesn't apply to your system, but something along those lines”. -- OK; - You uninstall this famous hotfix; - You reboot the machine so that the system cleans the residues; - Then you start again the installation; (sometimes) VISTA will answer again “this update doesn't apply to your system, but something along those lines”. Why ??? Like a prick with sharp, I have investiguated to try to understand; in particular if another hotfix had superseded this one or another thing of the same kind. I did not find anything. Therefore, I still did not understand : Why ??? Greetings and Happy New Year, Richard Quote Link to comment Share on other sites More sharing options...
Voodoo2man Posted February 10, 2008 Report Share Posted February 10, 2008 I think if SP1 is released, we know what its KB No. is, and every KB number higher then that is post SP1 (+- some updates which were released in the time after development of SP1 and release date) Quote Link to comment Share on other sites More sharing options...
Shoonay Posted February 11, 2008 Report Share Posted February 11, 2008 (edited) I think if SP1 is released, we know what its KB No. is [...]But we *do know* it's number already, since a early SP1 pre pre pre beta version! It's 936330. ... and, since SP1 Refresh 2 = RTM ... ... ... [...] every KB number higher then that is post SP1 (+- some updates which were released in the time after development of SP1 and release date)I've got a feeling it doesn't work that way. I've got about 200 "newer" files already, from 936344 to 947382. It's number doesn't correspond to the date nor turn of it's release, it's when they've found the bug or started working on it, prolly. Anyways, who cares? If you're unable to install the update, you'll not do it anyways, when Vista says it doesn't need it... Edited February 11, 2008 by Shoonay Quote Link to comment Share on other sites More sharing options...
Okaryn Posted February 17, 2008 Report Share Posted February 17, 2008 Hi, I'm using this method (not perfect !) : 1/ Install a clean vista without SP1 (or a futur Vista SP1 integrated) 2/ Install only the SP1 3/ Copy all the MSU file into a folder 4/ Execute the Auto-It source code below 5/ All MSU whose working with SP1 are move to the "OK" subdirectorie #include <GUIConstants.au3> $search = FileFindFirstFile("Windows6.0*.msu") If $search = -1 Then Exit EndIf $count = 0 While 1 $file = FileFindNextFile($search) If @error Then ExitLoop $count = $count + 1 WEnd FileClose($search) $search = FileFindFirstFile("Windows6.0*.msu") GUICreate("Windows Vista MSU Auto-Installer", 300, 50, $DS_SETFOREGROUND) $ID = GUICtrlCreateLabel("", 20, 10, 260, 30, $SS_CENTER ) GUISetState(@SW_SHOW) $progress = 0 While 1 $file = FileFindNextFile($search) If @error Then ExitLoop $progress = $progress + 1 GUICtrlSetData($ID, $progress & "/" & $count & " -- " & $file ) if runWait(@SystemDir & "\wusa.exe"& " " & @ScriptDir & "\" & $file & " /quiet /norestart", @ScriptDir, @SW_HIDE) <> 1 Then FileMove(@ScriptDir & "\" & $file, @ScriptDir & "\" & "Ok\" & $file, 9) EndIf WEnd FileClose($search) Quote Link to comment Share on other sites More sharing options...
phoenix Posted February 20, 2008 Report Share Posted February 20, 2008 (edited) Maybe someone should start a list of updates that apply to Post-SP1... Also, one could find out what KB or Updates are included in SP1 from Microsoft's website. Meaning, if it is not in the list then it is most likely Post-SP1. Edited February 20, 2008 by phoenix Quote Link to comment Share on other sites More sharing options...
xable Posted February 20, 2008 Report Share Posted February 20, 2008 With XP you can look at the files version numbers to determine which SP they are for. 5.1.2600.1229 5.1.2600.2229 I imagine it`s the same for vista, someone with SP1 will have to confirm that. Quote Link to comment Share on other sites More sharing options...
phoenix Posted February 20, 2008 Report Share Posted February 20, 2008 (edited) I am a little confused with Vista. I recently installed an update on Vista with just SP1 and received strange results. For example, here is one file that was in the update. 6001 = SP1 6000 = RTM usb8023.sys 6.0.6001.18000 1/19/2008 usb8023.sys 6.0.6000.20545 2/26/2007 Why would the update install if all the files are older? Shouldn't the top one be more up to date? Edited February 20, 2008 by phoenix Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.