locked
NVidia Geforce 8100/Nforce 620a driver causes Windows Home Server Console to deny access when provided with correct password RRS feed

  • Question

  • I have been unable to get any drivers for my Windows Home Server apart from the forceware 174.74 which is a beta. The drivers function great once I put hardware acceleration up but they cause my server to deny access from the console when I'm using a correct password for it (and when I plug my whs into a monitor the same password works!) and I'm at a loss here. I'm using a Biostar GF8100 M2G+ motherboard with an Athlon 64 X2 4400+ and all other drivers work fine but the graphics driver I found and I can't find a more stable one.
    Wednesday, September 30, 2009 4:04 AM

Answers

All replies

  • Use the VGA driver that ships inbox. Windows Home Server doesn't need a fancy video driver, since it's designed to be a headless device.
    I'm not on the WHS team, I just post a lot. :)
    • Marked as answer by Mightee Mo Wednesday, September 30, 2009 4:37 AM
    Wednesday, September 30, 2009 4:35 AM
    Moderator
  • That's what I did (after God knows how many installs!) ;-)

    Thanks though
    Wednesday, September 30, 2009 4:39 AM
  • Hi Martin,
    the FAQ How to handle error message “The Password is incorrect” attempting console access explains another workaround.
    Best greetings from Germany
    Olaf
    • Proposed as answer by Olaf EngelkeModerator Wednesday, September 30, 2009 10:28 AM
    • Marked as answer by Mightee Mo Wednesday, September 30, 2009 11:46 AM
    • Unmarked as answer by Mightee Mo Sunday, October 4, 2009 9:24 AM
    • Marked as answer by Mightee Mo Sunday, October 4, 2009 9:24 AM
    Wednesday, September 30, 2009 10:28 AM
    Moderator
  • There's one reason to upgrade the standard VGA driver:
    In order to use suspend you need a specific driver for your graphics chip set. This problems comes up every now and then and blocks standby.
    LightsOut - Power Management for Windows Home Server http://www.home-server-blog.de/add-ins/lightsout/#en
    Friday, October 2, 2009 6:31 AM
    Moderator
  • @ Olaf Engelke - I tried the registry entry listed in your workaround option 2 by disabling hardware acceleration to no avail and tried option 3 and got the error message "Cannot import [file] You can only import binary registry files from within the registry editor". As a result I had to go with your 1st option by uninstalling the Nvidia drivers from the system.
    • Edited by Mightee Mo Sunday, October 4, 2009 1:25 PM
    Sunday, October 4, 2009 9:28 AM
  • Yes, I noticed the standby function works when I have the driver installed but it seems to be impossible to keep the driver s it is unstable. You'd have thought Nvidia would have a better driver for their hsrdware isn't it?
    Sunday, October 4, 2009 9:30 AM
  • @ Olaf Engelke - I tried the registry entry listed in your workaround option 2 by disabling hardware acceleration to no avail and tried option 3 and got the error message "Cannot imort [file] You can only import binary registry files from within the registry editor". As a result I had to go with your 1st option by uninstalling the Nvidia drivers from th
    a registry file is merged with the system registry by simply double clicking it in Windows Explorer and confirm the warning.

    Did you save the file in notepad or did you use other software (other software like Word could produce special characters in the file, while it must be plain text)? 
    Did you copy all the lines, including the first line with Windows Registry Editor Version 5.00?
    Does the file have the extension .reg?

    Best greetings from Germany
    Olaf
    Sunday, October 4, 2009 11:05 AM
    Moderator
  • @Olaf - I followed your instructions down to the letter and copied the text from the page and gave it the extension .reg from save as all files in notepad. It just won't take it. Should I have typed it myself?
    Sunday, October 4, 2009 12:48 PM
  • ...
    You'd have thought Nvidia would have a better driver for their hsrdware isn't it?
    Last time I looked, nVidia had no video drivers for 32 bit server versions of Windows, and no plans to ever create them. They do have drivers for some video chipsets for Windows Server 2003 x64, but that's not useful for Windows Home Server. Often one can use a driver for Windows XP, but that's not always going to work.

    I'm not on the WHS team, I just post a lot. :)
    Sunday, October 4, 2009 1:33 PM
    Moderator
  • @ Ken Warren - The strange thing is Forceware 174.74 works perfectly apart from the console error and I think the driver is for Vista. All my other drivers are XP ones and they work fine. I've just stuck to your advice and used the standard VGA driver.

    Sunday, October 4, 2009 2:45 PM
  • @Olaf - I followed your instructions down to the letter and copied the text from the page and gave it the extension .reg from save as all files in notepad. It just won't take it. Should I have typed it myself?

    No, using notepad and saving should be enough. But in default settings Windows Explorer hides file extensions, therefore it could be, that your file has the extension .reg.txt.
    In Control Panel/Folder Options/View you can uncheck Hide extensions for known file types to make sure, that this is the case or not.

    Best greetings from Germany
    Olaf
    Monday, October 5, 2009 6:25 AM
    Moderator
  • I already unchecked the hide known extensions box also so I'm totally clueless as to what's going on
    Monday, October 5, 2009 10:52 AM
  • In my profile you find my email address, drop me a mail and I send the reg file to you directly.
    Another idea, what to check would be, right click your own file and select properties. Look, if there is a button like Unblock. If so, click it.
    (Also try to copy the reg file to the desktop of WHS first to ensure, there are no security mechanics blocking the merge.)
    Best greetings from Germany
    Olaf
    Monday, October 5, 2009 12:38 PM
    Moderator
  • Argh - a word ("Editor") was missing in that article:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]
    "SessionImageSize"=dword:00000020

    Sorry for that.
    Best greetings from Germany
    Olaf

    Monday, October 5, 2009 6:51 PM
    Moderator