Serious Bug for Add-In OnTheFlyUnzipper

It’s come to our attention that the add-in OnTheFlyUnzipper has a serious bug. If the add-in is uninstalled it will remove two Windows Home Server files with it. Good news though, the German Homeserver Blog says that the error was immediately corrected and a new version has been posted.

For those of you with a version lower than <1.0.5  installed, uninstall using the following information to avoid the Console crashing at startup: 

  1. Log in to the Home Server either locally or via Remote Desktop
  2. Open the folder C:\Program Files\Windows Home Server
  3. Make a backup copy of the files “WHSCommon.dll” and “qsmif.dll
  4. From within the console open Settings, Add-ins and Uninstall the OnTheFlyUnzipper add-in from the Installed tab.
  5. Put the backup copy of the 2 files back to their original locations
  6. Download the new 1.0.5 version ( unzip and put the OnTheFlyUnzipper.msi file into your Software shared folder under \\<ServerName\Software
  7. Re-open the console and install OnTheFlyUnzipper from within Settings, Add-ins, Available tab

A PDF User Guide on how to use OnTheFlyUnzipper, the add-in which automatically extracts uploaded ZIP or RAR archives is available for download from the following page, listed under OnTheFlyUnzipper (Guide(EN)).


AddThis Social Bookmark Button

Stop False Password Nags from the WHS Client

If you have installed Windows Home Server and previously had RC1 installed, or another machine on your network had the same name you are now using for WHS, chances are you might run into the situation where the WHS connector software on the client machine is always telling you that you need to “Update Your Password”.  Well, you will soon find out that no matter how many times you update it, the message never goes away.  It’s frustrating to say the least, and even when WHS says your password is out of sync with the server, you’ll find you can still access your shares and take backups.

The problem stems from the fact that on at least XP and Vista, Windows will store your credentials.  So if before you installed WHS you had another server on your network called “SERVER” then WHS gets confused about the old credentials being stored and no amount of updating your password seems to work.
If you run into this problem, on the client machine giving you problems go to your Start > Run window and type in:

rundll32.exe keymgr.dll, KRShowKeyMgr


This will bring up the stored credentials dialog.  Find your WHS name, highlight it and hit remove.  Logout of the client machine and then log back in.  WHS may ask you to update your password one last time.  Go head and do it and now you should notice that the WHS connector client stops falsely informing you that your passwords don’t match.

Guest Writer
Robert Stinnett

UPDATE by Philip Churchill – The above did not work for me until I done the following:

To finish, update your user password one final time through the WHS client:

Log on to the Windows Home Server Console
Click User Accounts
Right click the user and click change password
Type your password twice, even if its the same one!
Click ok


Some have also had success with the following as well, but only use as a last resort.
On the Client computer go to:
XP: C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys
Vista: C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys AND C:\Users\All Users\Microsoft\Crypto\RSA\MachineKeys
and see that the FOLDER AND ALL FILES in it have Full permissions for the Administrators GROUP and SYSTEM account.

AddThis Social Bookmark Button

The Knowledge Base is Expanding

Four more Knowledge Base articles have been published by Microsoft for WHS.

  1. You receive a disk-related error message or a network adapter-related warning message when you try to install Windows Home Server 939424.
  2. How to troubleshoot a problem that occurs when a digital media receiver cannot locate the Windows Home Server-based computer on a network 939425.
  3. You cannot connect to a computer that is running Windows Home Server 939758.
  4. A computer that is running Windows Home Server may appear two times in Network Explorer on a computer that is running Windows Vista 939759.


AddThis Social Bookmark Button

The first Knowledge Base articles for Windows Home Server at Microsoft

The first Knowledge Base articles for Windows Home Server have appeared on Microsoft. KB articles 939426, 939217, 939427, 939428, 939429 and 939218 all deal with issues relating to setup and backup. Lets have a look at them:

Article 939426 entitled Data may not be migrated or duplicated as expected in Windows Home Server explains why data may not be migrated or duplicated as expected if the Drive Extender feature in WHS is not working correctly. Details on how to start the Defilter.sys file system filter driver or the associated services if they are not started are given as well as advanced log troubleshooting steps.

Next is 939217. You may receive an error message when you try use a device or a program to access the Windows Home Server shared media folder. If you are using the Media Library Sharing feature in Windows Home Server to stream digital media to devices on your home network, an error message can appear if more than 10 devices try to access the shared media folder through Media Library Sharing.

Media Library Sharing in Windows Home Server has a 10-device limit. You may experience a situation in which this limit is exceeded. For example, another user may connect to the network by using a computer that is running Windows Media Player 11. If Windows Media Player has media discovery enabled, this computer may be counted as a device in Windows Home Server. This article explains how to clear the authorized device list in WHS.

Knowledge Base article 939427. Error message when you try to configure backup for a client computer in Windows Home Server: “The backup service is not running, please restart the console”. The “The backup service is not running, please restart the console” error message appears if the backup service has stopped responding. The article explains how to reset the WHS console before you connect to the server.

Next up 939428. Error message when you try to configure backup options for a client computer in Windows Home Server: “Cannot configure backup for this computer”. If error message “Cannot configure backup for this computer” appears when trying to configure backup options for a client computer, then the WHS Connector software is not installed correctly. The article explains how to uninstall and reinstall the Connector software.

Knowledge Base article 939429. Error message when you try to configure backup options for a computer in Windows Home Server: “The computer cannot be contacted”. This article explains why when you try to configure backup options for a computer in WHS, the error “The computer cannot be contacted. Make sure the computer is on and connected to the network and try again” occurs. This happens if the computer running WHS cannot communicate with the client computer and resolution steps are included.

And finally KB article 939218. Error message when you try to open a backup file in Windows Home Server: “Cannot connect to the backup service on the server”. This article explains that when restoring a file the error “Cannot connect to the backup service on the server. Verify that all services are running” can appear at approximately the 3% point. This occurs because a different administrator installed Windows Home Server Connector or the computer is running Microsoft Windows XP.

This problem occurs because Windows Home Server Connector installs a private key on the client computer when Windows Home Server Connector is installed. This action lets WHS authenticate the client computer. This private key is installed by using the default permissions and the default owner. The default owner of this key is not the Administrators group. Instead, the default owner of this key is the administrator who installs Windows Home Server Connector. Therefore, if more than one administrator is configured on the computer, only the administrator who installed Windows Home Server Connector can access the key. By default, no other administrator can access the key. The private key is required to start the restore operation from Windows Home Server. Therefore, only the administrator who installed Windows Home Server Connector can open the backup file.

Detailed resolution steps are explained on how to either manually set permissions on the folder that contains the private key or how to turn off the policy that restricts access to only the administrator who installs Windows Home Server Connector.

Well there we have it, the first six KB articles from Microsoft. Give them a read just in case you need them in the future!


AddThis Social Bookmark Button

Is there a Problem with your Security Certificate?

If you are using a computer without the connector (console) software on it (e.g. at work trying to access your home server) and you try to connect to the web interface of WHS then the following error appears:


Home PCs with the connector/console software installed have the server’s certificate automatically installed during connector setup. Computers without the software installed don’t have this certificate and so the error message.

To stop this error appearing; when accessing the web interface we need to export the certificate from a PC with the connector/console software on it and then import it into the PC without the software on it.


  1. So on the PC with the connector/console software on it open your web browser and type in your address
  2. To the right of the address bar click on the Padlock icon and then View certificates
  3. Click the Certification Path tab
  4. Double click the long GUID number (root certificate)
  5. Click the Details tab
  6. Click the Copy to File… button
  7. Export the certificate somewhere safe using default option


  1. Move the certificate to the machine without the connector/console software
  2. Double click the the .cer file and select Install Certificate… on the General tab
  3. Click Next on the wizard that opens and place a dot in Place all certificates in the following store
  4. Click Browse and select Trusted Root Certification Authorities and click OK
  5. Click Next and then Finish

That’s it. You can now access your web interface on your PC without the connector/console software via your dynamic address, your server name e.g. SERVER or localhost without getting the dreaded error html page.


Installing Connector on Home PC issues

If you are having problems installing the Windows Home Server Connector on your home PCs and having “join” issues, there is some great troubleshooting information to be found here.


My RC1 Installation Adventure

Well I went from Beta2 to the CTP build and yesterday to RC1. The sata hard disks were discovered correctly and no additional storage drivers were needed as was the same with the previous two builds. I did not even have to generate a new product key as any unactivated ones unused from the CTP build will work.

During installation the following screen appeared.

Disk Consistency

After checking, it carried on without any problem. This is the same screen I got in the CTP build also!

Under one hour later and after numerous re-boots all was completed but I noticed that I did not have network access. A check of Device Manager confirmed my suspicion that the LAN driver was not installed along with an SM Bus driver as these were not present on the CTP build either.

 Device Manager

Being two popular drivers* I do hope when the product goes RTM that these drivers are on the installation DVD.

After I installed the Connector CD Software on my 2 Vista and 1 XP Pro machines the following error appeared when right clicking on the WHS icon in the taskbar and then selecting “Shared Folders”.

Windows - No Disk

If I had the Connector Software CD in the drive the error did not appear. After some head scratching and a re-boot of each client machine the error disappeared. So after the Connector Software CD install make sure to re-boot the machine!

I checked the Date & Time on the General Tab under Settings and noticed that even though the time was correct that it was set to Pacific Time (US & Canada) under Time Zone even though I had set UK for both items in the setup “Regional and  Keyboard Settings” screen during the server installation.

1UK Settings

I also had Windows Update On to install updates automatically but found that after several hours, pressing the Update Now button on the same tab still found “lots” of updates. Two re-boots later and all of them were installed.

Apart from these minor niggles, this is an excellent build and appears more “solid” than previous releases.

*LAN Device = Integrated Realtek RTL8110SC Giga LAN Controller.

*SM Bus = “Intel 82801G (ICH7 Family) SMBus Controller – 27DA” from an Intel 945G & ICH7 chipset.