Hi.

I have script that hide KB971033 (hideKB971033.vbs). Is any way to integrate this with Win Toolkit?

This is VERY doubtfull we will help you out with this as it is VERY close to breaking the first rule of our forum...

However, the argument could legitimately be made that it would be nice to be able to hide a user specified update from showing up in WU. There are many cases that various updates are offered by WU to a user that for one reason or another the user does not wish to have installed, such as the 20 or 30 various language option updates I always have to hide. They are a real pain to have to hide one at a time. As such, I would be interested in seeing the OP's script, sanitized of course with no mention of any particular update number, if he would be willing to share.

Cheers and Regards

Edited May 25, 201212 yr by bphlpt

This is VERY doubtfull we will help you out with this as it is VERY close to breaking the first rule of our forum...

Sorry but you do not have right.

Forum rule:

Discussion of circumventing WGA/activation/timebombs/keygens or any other illegal activity will also not be tolerated.

I'm not asking how to crack the WGA. Installing KB971033 is not required by Microsoft. It's optional. I can install it but I don't have to do it. It's my choose. I have sript VBS that hide KB971033 from list in Windows Update. Thats all. I can manually hide KB971033 in Windows Update so why don't do this with script?

This is script that hide KB971033 from Windows Update lists and it's legal. This has nothing to do with cracking WGA. I can hide languages packs and I can hide KB971033.

Function WuaVersion 'get current WUA version

Dim oAgentInfo, ProductVersion

On Error Resume Next

Err.Clear

Set oAgentInfo = CreateObject("Microsoft.Update.AgentInfo")

If ErrNum = 0 Then

WuaVersion = oAgentInfo.GetInfo("ProductVersionString")

Else

Wscript.Echo "Error getting WUA version."

WuaVersion = 0 'calling code can interpret 0 as an error.

End If

On Error Goto 0

End Function

msgbox(WuaVersion)

if WuaVersion <> "0" then

Set ServiceManager = CreateObject("Microsoft.Update.ServiceManager")

ServiceManager.ClientApplicationID = "My App"

'add the Microsoft Update Service, GUID

Set NewUpdateService = ServiceManager.AddService2("7971f918-a847-4430-9279-4a52d1efe18d",7,"")

end if

'ServerSelection values

ssDefault = 0

ssManagedServer = 1

ssWindowsUpdate = 2

ssOthers = 3

'InStr values

intSearchStartChar = 1

dim strTitle

Set updateSession = CreateObject("Microsoft.Update.Session")

Set updateSearcher = updateSession.CreateupdateSearcher()

updateSearcher.ServerSelection = ssWindowsUpdate

Set searchResult = updateSearcher.Search("IsInstalled=0 and Type='Software'")

For I = 0 To searchResult.Updates.Count-1

Set update = searchResult.Updates.Item(I)

strTitle = update.Title

if InStr(intSearchStartChar, strTitle, "KB971033", vbTextCompare) <> "0" then

update.IsHidden = True

end if

Next

WScript.Quit

Question is: how to integrate this?

Edited May 25, 201212 yr by LittleCow

The problem with your script, if I understand it, is that it depends on Windows Update already having been run, or possibly running it as the script runs, I'm not totally clear on the syntax. Anyway, it seems it does not make any sense to try and integrate this with Win Toolkit since I don't think it would do anything at all. This seems to be intended to run after the OS is installed, WU has been run, and you just don't want to be offered the update anymore. So no need to integrate it with the OS. Just keep it on a Data disk or USB, run it once after you have made at least one visit to WU and you're good to go. I emphasize that I have NOT actually tried this script, just briefly looked at it. If I am wrong, I hope someone will please enlighten me. I was hoping for something that could be integrated, or run at first logon, to "inoculate" the OS even before the first visit to WU so I would never have to see "updates" that I know I don't want. But that might not be possible.

Cheers and Regards

Your agument is valid enough.

However I cannot make heads nor tails of your script and as bphlpt says I am fairly certain it won't work being integrated pre-installation.

That being said, it is still a valid request to be shown how to integrate a VBScript using WinToolkit, more or less turn it into an addon that WinToolkit can integrate or add to RunOnce, I don't personally believe it will help with this particular script, but it's still a valid request, so how about it? Anyone able to show us how to do that? Thanks in advance.

I would also appreciate it if the OP, or anyone else, could explain to me how this script is supposed to work. I'm sure I could learn something from it.

Cheers and Regards

However, the argument could legitimately be made that it would be nice to be able to hide a user specified update from showing up in WU. There are many cases that various updates are offered by WU to a user that for one reason or another the user does not wish to have installed, such as the 20 or 30 various language option updates I always have to hide. They are a real pain to have to hide one at a time. As such, I would be interested in seeing the OP's script, sanitized of course with no mention of any particular update number, if he would be willing to share.

Cheers and Regards

You don't need to hide them one at a time. You hide them in block. Ctrl+Click or Shift+Click then and hide them all selected.

Sure, if there is a way to implement in WinToolkit to hide all the languages outside the ones that you may actualy want would be a nice option.

As for updates, I like to have them all installed, just don't need all the languages.