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.

    HELP ME PLEASE WITH ERROR 0x7E

    Discussion in 'Windows OS and Software' started by martinneedshelp, Jan 31, 2009.

  1. martinneedshelp

    martinneedshelp Newbie

    Reputations:
    0
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    5
    hi
    i would like some help plz i just got a msi notebook GX 720 and when i go to turn it on a screen comes up with msi on it but then after few seconds it looks like its about to start but then a error comes up saying

    windows could not load required file WinSetup.dll. The file may be corrupt. To install windows, restart the installation. Errorr code:0x7E

    i have restarted it but comes up he same thing can someone plz help me
     
  2. Baserk

    Baserk Notebook user

    Reputations:
    2,503
    Messages:
    1,794
    Likes Received:
    1
    Trophy Points:
    56
    It seems you have a borked OS install.
    Have you installed the OS yourself or did it come pre-installed?
     
  3. martinneedshelp

    martinneedshelp Newbie

    Reputations:
    0
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    5
    what u mean by OS meant dont no many computer terms. wht i done was turn it on and it sed computer is booting up forf the first time this may take sometime and about half way it stops i thought was weild but then once the screen went were u can press the tab , selete and f11 to get the menus up that error came after it
     
  4. gerryf19

    gerryf19 I am the walrus

    Reputations:
    2,275
    Messages:
    3,990
    Likes Received:
    0
    Trophy Points:
    105
    drop your vista disk in the computer and restart--when it gets to the install screen, click REPAIR on the bottom left

    After a few seconds choose your install, then click on the startup repair link on the top
     
  5. Charles P. Jefferies

    Charles P. Jefferies Lead Moderator Super Moderator

    Reputations:
    22,339
    Messages:
    36,639
    Likes Received:
    5,070
    Trophy Points:
    931
    martin, do not make multiple posts on the same topic. That's bad forum etiquette and we do not allow it here per the forum rules. Your posts have been merged. Thank you.
     
  6. ascii

    ascii Newbie

    Reputations:
    0
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    5
    try re-installing Windows.

    ^_^
     
  7. DetlevCM

    DetlevCM Notebook Nobel Laureate

    Reputations:
    4,843
    Messages:
    8,389
    Likes Received:
    1
    Trophy Points:
    205
    First of all:
    I don't think that is the full error code - at least all the ones I ever saw were a bit longer. (also a lot of zeros)

    Next - try to explain your error a bit more "fluidly" in a slightly more "accessible way".

    But as said before - if you can't run through the initial instal process, either repair with a Vista disc or reinstal, as its a new laptop it won't be too much of a hassle.

    (Or return it if its new)
     
  8. ALLurGroceries

    ALLurGroceries  Vegan Vermin Super Moderator

    Reputations:
    15,730
    Messages:
    7,146
    Likes Received:
    2,343
    Trophy Points:
    331
    7E is too broad to diagnose. See this reference of stop codes. You could try extracting WinSetup.dll from a .CAB file on the windows CD that (hopefully) came with the computer.
     
  9. Shyster1

    Shyster1 Notebook Nobel Laureate

    Reputations:
    6,926
    Messages:
    8,178
    Likes Received:
    0
    Trophy Points:
    205
    There should have been four (4) error code parameters in parentheses, each in hexadecimal form, like so: 0x12345678, consisting of 8 digits following the "0x". If you provide us with those as well, we might be able to narrow the likely source of the error down somewhat.