DISQUS

Tech-Recipes: XP: Fix for Error: The procedure entry point GetIUMS could not be located | Windows installation | Tech-Recipes

  • Bzflag Addict · 5 years ago
    :D Worked perfectly !!

    Thanks Alex
  • Guest · 5 years ago
    :D Thank you Alex, I have tried typing this error message into Microsofts Knowledge Base and on the Dell pages with no luck. Through typing the message into google I came to your solution with perfect results. Once again.........thanks a million!
    Jaq
  • AlexTheBeast · 5 years ago
    It took me forever to find this information...

    Glad it could help you!
  • Anonymous · 5 years ago
    God bless you.
  • ljkdhall · 5 years ago
    B-E-A- utiful!!
    Thanks so much!!
    Larry
  • Anonymous · 5 years ago
    great trick!
  • Namons · 5 years ago
    can having this error appear hint at a deeper problem with the computer or hard drive?? I find the fact that many other websites site this file as adware very interesting as well.
  • Grateful · 5 years ago
    Man, what a tip! I didn't even know shift+F10 was available in setup mode. Got me around the problem. This occured when repairingreinstalling XP on an AMD Duron system hard drive that was going into an Intel box. Maybe that was related to the problem?
  • Another Grateful Person · 5 years ago
    Thanks, too, for posting great help.
  • Anonymous · 5 years ago
    Your solution freakin' rocks! Thanks for saving me a bunch of time.. worked like a charm.
  • blobbo · 5 years ago
    well you havent actually fixed anything , but gotten rid of the error message .....LAME
  • davak · 5 years ago
    <ul id="quote"><h6>blobbo wrote:</h6>well you havent actually fixed anything , but gotten rid of the error message .....LAME</ul>

    lol

    If you are repairing and hit this error, your options are either...

    a- reformat and reinstall
    b- hit OK a million times until the install continues
    c- do the work around above

    I think this is why people are so appreciative of the above fix. The error isn't fatal... it just prevents the repair from completing.
  • Shams · 5 years ago
    It worked!!!!!!

    Thanks a lot!!!!!!
  • KeepOnSwimming · 5 years ago
    Saved me from formatting my HD.

    Love you!
  • delaluna · 5 years ago
    That worked great!
  • bukarr · 5 years ago
    Best advice yet, imindebted...
  • Jonathan Lippe · 5 years ago
    Thanks !

    Worked for me too. I have been trying to get windows to work after receiving the winsrv stop: c0000135 error. Everyone else that got the error was because they installed SP2. I didn't install it, but got the same blue screen. So here I stand having to do a repair install. I wonder what will happen to the PC.
  • KLoye · 5 years ago
    Just another thanks in a long line, I'm sure. Saved me sooooo much time.
  • lortech · 5 years ago
    Seems to me Microsoft should log into Tech. It really urks me that they go to all the trouble of creating an error response, but you cannot ever find the error at their site. Does anyone know what the error is tho? Does if affect future performance?
    Thanks,
    Laurie
  • adamant · 5 years ago
    Thanks Mate! Worked like a treat.
  • ronalan · 5 years ago
    :D
    :!: You're a god among mortals.............THANKYOU THANKYOU!!!!!!! Your simple fix was magic...
  • jurgen · 5 years ago
    thanks it worked
    Jurgen :D
  • mx|nuTTy · 5 years ago
    Command prompt can be found through the install?

    :twisted:

    This could get interesting.

    -x-
  • Anonymous · 5 years ago
    <ul id="quote"><h6>Guest wrote:</h6>:D Thank you Alex, I have tried typing this error message into Microsofts Knowledge Base and on the Dell pages with no luck. Through typing the message into google I came to your solution with perfect results. Once again.........thanks a million!
    Jaq</ul>

    I don't even get a command window with shift F10, and there is no UNREGMP on my processes screen
  • Anonymous · 5 years ago
    i get this error when i try to run application in vb.net
    i did tried to reinstall win xp and it was in other directory ..
    any one has any idea?
    i tried to change msdart.dll file also..
    other than this i m not getting this error at any where or doing anything in my computer .
    thanx
    Nilesh
  • EJamNT · 5 years ago
    I want to thank you very much for the information on this issue. I did exactly as the directions stated and it worked. I was ready to use my PC as a boat anchor. Thanks again

    EJamNT
  • sambones · 5 years ago
    Thnx a million Alex. i messed with that thing for half an hour then decided to google it and fixed in three mins. really appreciate your posting on this :D
  • phenotype · 5 years ago
    Same comment about the google search and naturally my grateful thanks. Honest, thanks for taking the time to post this solution!

    Best, Aaron
  • Anonymous · 5 years ago
    <ul id="quote"><h6>phenotype wrote:</h6>Same comment about the google search and naturally my grateful thanks. Honest, thanks for taking the time to post this solution!

    Best, Aaron</ul>

    yeah once you end the process then you have another problem in side of wondows !
  • Marco · 4 years ago
    Thanks Alex

    This stuff was really annoying
    I found tenths of people on ithe web looking for this fix.
    Great
  • Wilmer · 4 years ago
    Hey, I got that message talking about it couldn't find the app or whatever... man listen.. I did that shit f10 thing you said i ended that app and it kept downloading fine.. thanks a lot for posting this message man, i'm pretty sure you have helped a lot of people
  • Anonymous · 4 years ago
    Rock on! Worked like acharm! Thanks Thanks Thanks!!!!!!!!
  • Recording_fil · 4 years ago
    Thanks for the inspiration to continue on and not format the drive, but when I pulled up the task manager I could see that all my cpu usage was in idle and the installation had stopped. So... we started hitting ok and withing a minute or two it took off and started installing again. It went for a few minutes and then we had to do it again, but it's obvious when it goes back to the installation.

    Also we waited about 30 minutes before startin with the hitting ok.
  • Anonymous · 4 years ago
    That has saved more a lot of time!!! :D
  • compudork · 4 years ago
    Thanks a lot! :D Great useful information!
  • session · 4 years ago
    u legends thx for help keep postin always great to read
  • Anonymous · 4 years ago
    I was having the same trouble for the last 6 hours nad found your solution. Thanks it worked!!!!!!!! :D