Sometimes when trying to find particular updates and troubleshoot Windows update problems you need to be able to manipulate the update data. Using the ‘installed updates’ applet is not always practical. I use the below script to give me a .csv files with all updates installed on a machine.
If you use an AWS Storage Gateway as your virtual tape library you may accidentally move one (or more) of your tapes to archive (export in Backup Exec). Once you initiate this process there is no way to stop it in the AWS console! You will just see the Transfer to VTS message and have to wait a very long time. Fortunately you can stop it using the AWS CLI. You will need your gateway arn and your tape arn (you can find these in Backup Exec) and stop the transfer one tape at a time.
This is just a quick reference for anyone trying to quickly pull off a list of installed software from a remote machine. You will need the remote registry service (you can start this remotely from the services console) and WMI service running on the remote machine.
I wrote this script to handle a company wide Keepass update in my company. The script checks to see if a file (with the name of the version of Keepass) exists. If it does then it proceeds with the install, if not it closes the program.
This has been a source of irritation for many recently. Simply disabling wake timers and disabling the Windows Update service is no longer enough to keep Microsoft from waking your machine from sleep mode to carry out maintenance and install updates. It looks like this was introduced as an update sometime in 2018 and affects Windows 10 1607, 1703 and 1709. Fortunately there are a number of steps you can take to stop Microsoft meddling with your machine and leaving it running all night costing you larger electrical bills.
This is a quick post to mention a fix for an annoying problem that cropped up today after Sage had been installing their applications on one of our servers. It first appeared that Windows was not activated (even though I knew I had done this) and the Software Protection service was unable to start. It was giving the error Windows could not start the software protection service on Local Computer. You may also notice that Microsoft Office pops up with an error stating Microsoft Office can’t find your licence for this application. A repair attempt was unsuccessful or was cancelled. Microsoft Office will now exit. I experienced the error on Windows 2012 R2 Server but it seems that this is common on all operating systems above Windows 2008 R2.