By Philip Churchill on November 25th, 2008
Microsoft Fixes 6 Issues with WHS
Earlier today an update for Windows Home Server became available. Known plainly as "Windows Home Server Update, November 2008" or KB957824 the minor software update fixes 6 problems that users have experienced over the following months with Windows Home Server:
- Improves the interaction between home computers that are running Windows Vista and a Windows Home Server computer when copying files or folders to a shared folder on WHS..
- Sometimes, WHS generated lots of notification messages about the files stored in shared folders, causing high CPU utilization and slow performance on the server. After this update is installed, applications such as the Microsoft Zune software, that may be running at the same time, no longer consume excessive processor resources.
- Under certain conditions, WHS disabled duplication on shared folders after a new user account was created. After this update is installed, the creation of user accounts no longer affects the status of shared folder duplication.
- When restoring files and folders from WHS the process may stop when it is 79% complete. New functionality to help prevent this issue is provided within this update.
- When restoring files and folders from a Home Server Backup from an external hard disk drive to the software shared folder on WHS some issues could occur. This update adds functionality to prevent the unintended restoration of older versions of the WHS Connector software from overwriting newer versions of the files.
- This update improves the search functionality when using remote access by allowing you to use accented characters with the Remote Access search.
The update will be downloaded automatically to your Windows Home Server via Windows/Microsoft Update, as long as Automatic Updates is enabled on the server. If not from within the Windows Home Server Console, click Update Now on the General page of the home server Settings page to receive the update.
More information is available in Knowledge Base article 957824 from Microsoft.
Share this WHS Article with Others:
Well, looks like Microsoft blew another one. The article clearly states that a reboot is not required, but it is. Then the Home Server Connector is hosed on ALL of my PCs. I have manually uninstalled and reinstalled as well as letting the connector installer handle the uninstall to no avail. Immediately following the connector install, I get a prompt from the tray icon notifying that there is an update available, but the upgrade fails with the message “The operation cannot be completed at this time”.
Update for Windows Home Server (KB957825) is buggy (crap) then the Home Server Connector is hosed on ALL of my PCs, I get a RED Windows Home Server Console icon after installing KB957825 not Green saying that the Console software has to be updated. Could not find a new Console Software version. After hours of trying to fix this I uninstalled KB957825 manually and rebooted the server, guess what I now get a green Home Server Console icon again. Well, looks like Microsoft blew another one is so right.
same here.
I’m also having an issue but with Windows Media Connect. When I log into my server via RDP I get an error says Windows Media Connect needs to close. The error keeps popping up every time I close the message.
This may be because I’ve upgraded the Windows Media Player to version 11 so I could stream to my PS3. I guess Microsoft wouldn’t both testing for that since your only supposed to have WMP10 on there.
-Sean
OK, I fixed my problem.
Ok. So I moved my connector software back to “\\servername\software
home server connector software” and un installed/re-installed the update. I then reinstalled the connectors by running setup.exe from the connectors software folder and everything works fine.
\\servername\Software\Home Server Connector Software
Noted that WHSConnector.MSI now has a date of 31/10/2008… previously I believe that the date was 10/07/2008
Ran WHSConnectorInstall.exe and let it finish the install… succesfully got to the console.
Ran the tray icon it came back green this time..
Since the 957824 fix I cannot open a backup more than once without restarting the client. I get a message that the computer could not connect to the backup service on the server. I checked the service and the service is running.
On my mapped network drives (mapped to my user folder on WHS) I’m getting strange numbers. Total size is 212GB, free space is 440GB? Total size used is some garbage number. This is happening on all our PC’s — both Vista and XP. What the heck is going on here? I’m worried now that data corruption might be lurking ready to bite.
The ‘strange’ numbers are a result of the new free space rules introduced in the update. These are to show Vista in particular, that there is more free space available; previously, Vista could only see the free space on D: no matter how much you had. Now, it sees the total free space available to it as well. For you, I would imagine your D: space is 212, while Vista can now use 440.
It’s nothing to do with data corruption
The update now uses the “quota” size for calculating free space. This allows for a lot more space than is actually on the D:\ drive.
When the new update ( KB957825 ) was automatically downloaded my connector icons turned red. It said there was a new version of WHS connector is available on server. When I tried to install the upgrade, I get an error. I’m logged in as administrator, I’ve turn off my antivirus and fire wall on my PC’s and server. It still will not upgrade. Its say’s the newer version is 6.0.1800.0. I’ve uninstalled the existing connector, restarted my pc and installed the new version from the sever. The connector version is now 6.0.1800.0 I still have a red icon’s and the severs does not see My PC’s.
I have three pc’s on my network, one running vista home the other two running XP. I built my WHS about two months ago, which ran fine till the upgrade. ANY suggestions
Sparky 369 I had the same issue until:
Ok. So I moved my connector software back to “\\servername\software\
home server connector software” and uninstalled(reboot)/re-installed the update(reboot).. I then reinstalled the connectors by running setup.exe from the connectors software folder or click on the red connector icon and everything works fine.
\\servername\Software\Home Server Connector Software
Noted that WHSConnector.MSI now has a date of 31/10/2008… previously I believe that the date was 10/07/2008
Ran WHSConnectorInstall.exe and let it finish the install… succesfully got to the console.
Ran the tray icon it came back green this time..
Note servername is the name of your server.
Yeah. I guess I should have posted earlier to state that I figured it out and solved my problem. I did the same thing that KevinS did.
It appears that me must fight our need to organize our WHS Software folder too much. The Home Server Connector Software folder must remain on the root of the share and not be moved to a more logical location like \\servername\software\WHS Software\Home Server Connector Software. It would have been nice if Microsoft had found a way to lock this folder down or warn you if you tried to move it. Oh well, that may be technically impossible or just not worth the effort to them.
Anyway, I am back up and running normally.
I just installed my WHS today. I was able to copy all of my photos to the server. After that I realized that I had to update the server, which I did. Now I cannot copy any files to the server without getting a “Cannot Copy ****.***: Access Denide. Make sure disk is not full full or write protected and that the file is not in use.”
None off the above apply. The only way that I have been able to copy file over is through logging on via the web browser. Can someone help?
Russell, after updating the WHS did you update the connector on your PC?
Update worked fine for me… Updated all my connectors on my pcs flawlessly.
Same problem here. 4th March 2009, I hav the message “the operation cannot be completed” when trying to install the new connector upgrade from the system tray popup. Stupid Microsoft.
Uninstalled and reinstalled the connector and it all seems fine now. Do those clowns in Redmond actually test any of their s/w?