The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Signed driver problem

    Discussion in 'Other Manufacturers' started by Klemme, Sep 16, 2007.

  1. Klemme

    Klemme Newbie

    Reputations:
    0
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    5
    I encountered a strange problem the other day:

    I normally just close the lid on my 6625WD then I'm done using therefore it is not often that I reboot my pc. But the other day I did reboot and then my strange problem happened: I couldn't get on the internet or the local network.
    After several hours of headscratching and trying different things with no luck I looked in the Event Viewer under Applications, and io and behold: the TCP/IP Protocol Driver failed to start because the driver wasn't digitally signed. I tired "everything". I reinstalled my wireless network card, my wired network card, the TCP/IP service.

    I eventually had to use system restore to get everything working again and it have worked ever since.
    Now I use Vista Ultimate 64bit OEM from Zepto and I have heard the the 64 bit version of Vista is very strict with non-digitally signed drivers, which is okay. But how on earth is it possible to replace the driver and then afterwards refuse to start?

    Hope some of you smart people can shed some light on this!

    Klemme
     
    Klemme, Sep 16, 2007
    #1
  2. John Ratsey

    John Ratsey Moderately inquisitive Super Moderator

    Reputations:
    7,197
    Messages:
    28,841
    Likes Received:
    2,166
    Trophy Points:
    581
    I believe that Microsoft recently issued a patch which enforced driver signing more rigorously than previously. I suspect this downloaded and installed itself after your previously reboot. More here.

    The question to answer is whether your system restore removed the Microsoft patch or found a suitably signed driver which the patch allows to run.

    John
     
    John Ratsey, Sep 16, 2007
    #2