Sophos Auto Update Error – Installation could not upgrade the current version of product SAVXP – Windows 7 64-bit

Copy the destination files in the bullet list to folder  C:\Program Files (x86)\Sophos\Sophos Anti-Virus\

  • native.exe from C:\ProgramData\Sophos\AutoUpdate\Cache\savxp\native\amd64\
  • All files from C:\ProgramData\Sophos\AutoUpdate\Cache\savxp\drivers\onaccess\win7_amd64\
  • All files from C:\ProgramData\Sophos\AutoUpdate\Cache\savxp\drivers\boottasks\win7_amd64\
  • All files from C:\ProgramData\Sophos\AutoUpdate\Cache\savxp\drivers\sdcfilter\win7_amd64\

Right-Click Sophos Icon from the taskbar and run update now. Sophos should update now and the latest IDE should appear in the C:\Program Files (x86)\Sophos\Sophos Anti-Virus\ folder

Solved – You may not have permission to access this network resource


Note: The below solution is considering the computer you wish to connect to is turned on; has sharing enabled, has the sufficient right active and you are able to ping to it

Solution (Applies to Windows 7 / Windows 8 / Windows 8.1)

  • It is most likely that this folder was accessed with a wrong password earlier
  • Open Control Panel – User Accounts
  • From the left panel – Click Manage your credentials


  • For Windows 8 and 8.1 users the Web and Windows Credentials will show separately. Click Windows Credentials
  • Under Windows Credentials; the PC name or IP Address that you were trying to connect to must be listed


  • Click Remove to delete the existing credential
  • Once done; try accessing the shared folder once again.


Start Menu for Windows 8.1

Get your Start Menu Back for Windows 8 and Windows 8.1

Personally, I thought I too would move on with the Microsoft trend and never get back to using the Start Menu again. After months of toiling with the crippling interface; I was done with it and needed my Start Menu back.

Class Shell is the perfect Start Menu solution for all the freebies available on the web. No ads; No unwanted mess; No promotion links; No tinkering with the registry settings. In short; its just gives you what you want. A perfectly working Start Menu that can actually make you start liking Windows 8.1 for what it is made for.

Though its a free tool; one wouldn’t shy away from donating for their effort

Download Link for Classic Shell

It can be used on Windows 7, Windows 8 and Windows 8.1

Android SDK Manager Failing to Load

Android SDK Manager wont open

It’s always a pain in the <you-know-where> when you lose your hard disk to time. Some must be frowning at this statement asking ‘What’s the big deal in this cloud era?’. Well some or most of the data may be somewhere in the skies but getting everything back and setting up one’s development environment to whereever she was, is a real pain as what happened to me few weeks back when I lost my good old HP laptop.

So, I was setting up my Android developement environment on my new laptop with latest available ADT bundle and JDK. But when trying to launch the SDK Manager it was just failing to load and never left a trace of what went wrong. In my case the problem turned out that ADT was unable to locate the private JDK installation. To diagnose, the first thing you can do is to launch a command window, type set JAVA_HOME there, press return key and see if it prints out any directory locations. If it doesn’t, Bingo, thats the deal.

Now, to fix this issue there are two ways, pick the one that suits your level of hackerdome.

  • Option 1 : Set up your JAVA_HOME environment variable from Control Panel > System  and launch SDK Manager (Refer to screenshot below)


  • Option 2: Modify<sdk-root>\tools\android.bat to point to the required JDK/JRE location as shown below
    • (Here be dragons: Try this only if you have some clue to on how batch files work)
    • Locate the line that says “set java_exe” , assign the path to java.exe,  comment out the next two lines as shown below, save the file and then try launching SDK Manager



TL;DR: Android SDK Manager fails to start without showing any error messages and with possible one single blink of a black window? The ADT has no clue where to locate JDK/JRE on your PC. Either fix your PATH variable to point to a JDK/JRE location or edit <sdk-root>\sdk\tools\android.bat file in the next line where you see the comment ‘Check we have a valid Java.exe in the path’

Get-WmiObject : The RPC Server is unavailable

Error Message when running Get-WmiObject cmdlet on a Remote Machine

Get-WmiObject : The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
At line:1 char:1
+ Get-WmiObject win32_bios -ComputerName remotecomputername|Select PSComputerName,Manufact ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 + CategoryInfo : InvalidOperation: (:) [Get-WmiObject], COMException
 + FullyQualifiedErrorId : GetWMICOMException,Microsoft.PowerShell.Commands.GetWmiObjectCommand

Verify DCOM Settings on Remote Machine

  • The first step is to check is if the DCOM Service is enabled in the Remote Machine
    • From the remote machine; From the Start Menu; type dcomcnfg
    • Open Computers – Right Click My Computer – Properties
    • If the checkbox for ‘Enable Distributed COM on this computer ‘ is ticked; you have got through the first step. By default this option is always enabled



Check the Windows Firewall on Remote Machine

  • The next step is to check Windows Firewall. It is most likely that your firewall is enabled.
  • For testing purposes, please disable the Firewall on the remote machine and test the script. I’m sure you have got the result. If not, I would sadly request you to look for answers elsewhere 😦
  • It is not advisable to disable your Firewall to get this working and most of all if you are administering a network of over 100 or 1000 machines this is not practical either. So the best way is to identify the Communication Port that was blocked when running the script. So turn back your Firewall On.

Enabling Logging on Windows Firewall and Identify Blocked Port on Remote Machine

  • From Advanced Settings of your Firewall; right click Windows Firewall with Advanced Security on Local Computer and select Properties
  • From the Domain Profile Tab; click Customize under Logging
  • Select the Yes drop-down for Log dropped packets
  • Take note of the Logfile Location and filename from the name field
  • Click Ok to confirm



  • From your PC or a Server PC; run the Get-WmiObject cmdlet once again so as to receive the error
  • From the remote machine; run Notepad as Administrator and open the pfirewall.log file
  • Identify the Drop Action from the Firewall that points to the time we ran the Get-WmiObject cmdlet and the source-ip (src-ip) of the machine you ran the script from
  • Take note of the Protocol TCP/UDP and Destination Port Number (dst-port) Eg: 49155
  • You can enable an Inbound Rule for this your problem will solved. If you are administering a large network; apply this to a group policy instead.


Movie Maker 2012 does not run on Windows 7 32-bit/64-bit

After installing Movie Maker, you face the below error as illustrated


You may go through the link that shows up in the error and check the minimum system requirements. The only pointer that may catch your attention is the DirectX Version on your PC. The minimum DirectX Version expected is version 9.

To crosscheck this click Start – Type Dxdiag and press enter. The DirectX Version will be listed in the DirectX Diagnostic Tool Window that opens up. If your PC is relatively new and frequently updated; there is no reason why your DirectX Version should be below 10; so forget the minimum requirement of DirectX 9 for Movie Maker 2012


The most obvious solution to get your Movie Maker software working is to update your Display Driver

  • Locate your Display Driver Model and Driver Version
  • Start – Control Panel – Device Manager


  • As per the illustration, the display card is Intel and hence I will proceed to the Intel Website to download and Install the latest driver (
  • But if in your case; it’s an NVIDIA proceed to this link instead (
  • Locate your driver using the search options available on the respective Driver Manufacturer webpage.
  • Download and Install the latest updates
  • Once done, restart the PC and try running Movie Maker