WSUS Error – Windows Update Failed 80244017

August 13, 2014 Leave a comment


Using WSUS and clients getting an error on install – Windows Update Failed 80244017


Even though Domain Users had Read/Write access I was able to fix this error by adding WSUSServer\users with read/execute privileges to the WsusContent folder and it’s subfolders.


Regedit.exe – File System Error (-1073741819)

July 11, 2014 Leave a comment

Problem: I was watching (via console) another administrator trying to run regedit.exe however the following error was occurring;


File system error (-1073741819)

Resolution: Turn off UAC.

Putting Exchange Server into Maintenance Mode

July 8, 2014 Leave a comment

Run PowerShell as Admin to put server in maintenance mode for patching or other work.

1. Set-MailboxServer “name of server” -DatabaseCopyActivationDisabledAndMoveNow $True
2. Set-ServerComponentState –Identity mtaexch01 –Component HubTransport –State Draining –Requester Maintenance
3. Suspend-ClusterNode –Name “name of server”
4. Set-MailboxServer –Identity “name of server” –DatabaseCopyAutoActivationPolicy Blocked

Take server out of Maint Mode

1. Set-MailboxServer –Identity “name of server” –DatabaseCopyAutoActivationPolicy Unrestricted
2. Resume-ClusterNode –Name “name of server”
3. Set-ServerComponentState –Identity “name of server” –Component HubTransport –State Active –Requester Maintenance
4. Set-MailboxServer –Identity “name of server” –DatabaseCopyActivationDisabledAndMoveNow $False

Error: (unknown): TIMEOUT – READ_DMA retrying (1 retry left) LBA=493207

July 4, 2014 2 comments


I am running a pfSense 2.1.3-RELEASE-nanobsd virtual machine on VirtualBox as a firewall as part of my study network (great way to do domain labs etc. with access to internet without interferring with corporate environment).
The pfSense firewall would constantly get the following error and stop routing (would require a reset).
Error: (unknown): TIMEOUT – READ_DMA retrying (1 retry left) LBA=493207


In VirtualBox settings of the pfSense vm, disable USB and/or remove Floppy.

VMware – The VMware VirtualCenter Server service depends on the following service: ProtectedStorageerver

July 4, 2014 Leave a comment


The VMware vCenter was not started.

Noticed that there were 5 services not starting, was getting the following error;

The VMware VirtualCenter Server service depends on the following service: ProtectedStorage. This service might not be installed.


Backup Registry before making changes.

Remove the “ProtectedStorage” as dependency in the registry, and vCenter will start fine.

You can find it in :


In DependOnService you can remove the ProtectedStorage
After reboot it works fine.

VMware vSphere web client – Error 1053: The service did not respond to the start or control request in a timely fashion

July 4, 2014 1 comment


Was unable to start the VMware vSphere Web Client after upgrading from 5.1 to 5.5

Noticed that the VMware Vsphere web client service wasn’t started.
Tried manually via Services.msc got the following error;
Windows could not start the VMware Vsphere web client service on local computer.
Error 1053: The service did not respond to the start or control request in a timely fashion.


I realized that the folders in the new version installation had changed and for that reason paths should be changed also.


Check your Registry value for hkey_local_machine\system\currentcontrolset\services\vspherewebclientsvc:


“C:\Program Files\VMware\Infrastructure\vSphereWebClient\server\bin\service\bin\wrapper.exe” -s “C:\Program Files\VMware\Infrastructure\vSphereWebClient\server\bin\service\conf\wrapper.conf” set.default.SERVER_HOME=C:\Program Files\VMware\Infrastructure\vSphereWebClient\server set.default.JMX_PORT=9875

Look at these value and confirm that the WRAPPER file is located and accessible on the path mentioned above.

Always backup your registry before making changes.

For me I had to change the port (see below) for it to work, for others I have seen it is due to the path being incorrect or inaccessible.

“C:\Program Files\VMware\Infrastructure\vSphereWebClient\server\bin\service\bin\wrapper.exe” -s “C:\Program Files\VMware\Infrastructure\vSphereWebClient\server\bin\service\conf\wrapper.conf” set.default.SERVER_HOME=C:\Program Files\VMware\Infrastructure\vSphereWebClient\server set.default.JMX_PORT=9877

Restart the server.

Backup Exec 2014 Agent Install – Error: Failed to execute VC 10.0 runtime installer. Error code 1603

July 4, 2014 Leave a comment


Downloaded and installed Backup Exec 2014 onto the Media Server and then went to one of our servers to update the Agent for Windows.
Previously I have just copied the RAWS32 & RAWS64 folders from “%ProgramFiles%\Symantec\Backup Exec\Agents” path on the media server and put onto a network drive, then run the installs from there. I do push installs for LAN Servers but I do the manual installs for Servers in DMZ.
This time however I got the following error:
Return Value of Microsoft Visual C++ 2010 Redistributable (x64) : 1603
+ 06-11-2014,21:17:12 : ERROR: Failed to execute VC 10.0 runtime installer. Error code 1603.


Just copy the VCREDIST folder along with the RAWS32 or x64 from the “%ProgramFiles%\Symantec\Backup Exec\Agents” directory and run the correct RAWS setup.exe locally on the server.



Get every new post delivered to your Inbox.