8 responses to “Windows Home Server Users: Avoid Latest ForceWare Drivers”

  1. Nvidia Driver Issue with Windows Home Server « MS Windows Home Server

    [...] release has no mention of a compatibility issue in their release notes, although fellow enthusiast Christopher Price and myself have experienced this [...]

  2. Bill Ankstrum

    Oh man. I have been experiencing this since October! It hadn’t even occured to me that it could be a graphics driver issue. Wow. Any resolution to this issue?

  3. Bill Ankstrum

    Oh man, that’s terrible! Wishing you the best on your system recovery.

    I uninstalled the nvidia graphics drivers and was able to log in via Remote Desktop. However, now the connector software can’t see the home server. Man, this is a mess.

  4. Liveblogging Windows Home Server: Death & Rebirth | Christopher Price .net

    [...] Wednesday, I was doing some regressive bug testing for Microsoft on a Windows Home Server (WHS) bug. When I flipped the power switch on my power supply, the power supply exploded… literally. [...]

  5. Yak

    I also had the same problems following the Jan 09 WHS updates.

    I found a work around using a registry entry from here that should hopefully work for older nVidia cards that can’t use the latest nVidia drivers;

    http://blogs.technet.com/brad_rutkowski/ar…ed-to-load.aspx

    http://forums.nvidia.com/index.php?showtop…sktop&st=60

    Incidentally, when I removed the registry edit and upgraded my nVidia drivers to the latest version, the registry modification also appeared on my WHS.

    Have documented more fully the steps I took here

    http://forum.wegotserved.co.uk/index.php?showtopic=6162

  6. Yak

    The first two links in my previous post that don’t appear to work are properly linked to from in the wegotserved forum post.

    Alternatively if you use the search term

    brad rutkowski + rdpdd.dll failed to load

    in google it is the first link found. In Brad’s Server 2003 blog post there is a link to the nVidia post.

Leave a Reply