v0.8: Issue by processing of disableupdates.cmd

[Former user]

Hi Matthew,

I have just discovered your project as I looked around for an alternative to the discontinued Aegis-voat script. Many thanks for the impressive rework of the very useful script.

During the run of the script, when the subscript disableupdates.cmd has been called, an additional empty cmd windows emerged and another wusu.exe error poped up (see attached screenshot). I have not touched the two extra popups and have observed the main console until the script finished. In the main script console windows however everything seams to have been done alright with the final statement 'completed successfully'. But in the logfile I found this lines:

Uninstalling and Disabling Windows Updates: 
Method invocation failed because [System.String] doesn't contain a method named 'IsNullOrWhitespace'.
At D:\Downloads\Ancile\Ancile_0.8\scripts\updates\UninstallAndHideUpdates.ps1:55 char:34
+ if (![string]::IsNullOrWhitespace <<<< ($KBFile)){
    + CategoryInfo          : InvalidOperation: (IsNullOrWhitespace:String) [], RuntimeException
    + FullyQualifiedErrorId : MethodNotFound

Computer Name: Laptop

Now I'm not sure if the disableupdates.cmd has really done the job at all.

#!
OS Name:      Microsoft Windows 7 Professional 
OS Version:    6.1.7601 Service Pack 1 Build 7601
System Type: x64-based PC

I hope it will help you to evaluate the problem.

Best wishes Scalar

[Matthew Linton]

Thanks for bringing this up.

With this error, the disableupdates.cmd definitely didn't uninstall and hide the updates that it should have. I believe this is an issue caused by running an older version of powershell.

If you can, run the following command from within powershell and post the output here.

PS C:\> $PSVersionTable

This command will just help me confirm your powershell version information.

To get this running, you have two options:

• Install the latest version of powershell (https://msdn.microsoft.com/en-us/powershell/scripting/setup/installing-windows-powershell).
• Wait for me to release a fix. I'll post here when a fix is ready to be tested.

[Former user]

Hi Matthew,

thanks for the prompt respond. This is the output of my powershell:

#!
PS C:\Users\Admin> $PSVersionTable

Name                           Value
----                           -----
CLRVersion                     2.0.50727.5485
BuildVersion                   6.1.7601.17514
PSVersion                      2.0
WSManStackVersion              2.0
PSCompatibleVersions           {1.0, 2.0}
SerializationVersion           1.1.0.1
PSRemotingProtocolVersion      2.1

I'll check tomorrow to upgrade the powershell ...

Cu Scalar

[Matthew Linton]

Great, thanks

[Matthew Linton]

I've updated Ancile (v0.9.1) with changes that should allow you to run it under powershell v2

https://bitbucket.org/matthewlinton/ancile/downloads/Ancile_0.9.1.zip

Let me know if that fixes things.

[Former user]

Hi Matthew,

Thanks for fixing the issue with the powershell incompatibility. Just for record: I upgraded the PS to v3 on one of my Win7 machines and the Ancile v.0.8 has done everything fine. Today I used the new Ancile v0.9.1 on machine with PS v2 and it has also done the job fine.

The issue can be seen as resolved :)

CU Scalar

[Matthew Linton]

Glad to hear this resolved your issues. Thanks for all your help testing Ancile.

RESOLVED

[Matthew Linton]

Fixed in version 0.9.1 (Tested)