Win XP Repair Install Hangs on Unregmp2 GETIUMS procedure entry point cannot be located.

can't do that. The repair reinstall is not complete so I cannot boot up XP Home.
I have tried twiice and both times it comes up with this error.

danjava

Check these links for info on repairing XP:

 http://www.webtree.ca/windowsxp/repair_xp.htm (Last Known Good/Safe Mode/Recovery Console/Repair)
 http://www.michaelstevenstech.com/XPrepairinstall.htm
 http://www.windowsreinstall.com/ (Choose Pro or Home from the side-bar)
 http://support.microsoft.com/default.aspx?scid=kb;en-us;315341
 http://support.microsoft.com/default.aspx?scid=kb;EN-US;306084 (Restore to previous state)

thanks for your advice. I am able to get into the recovery console, and whether I rename msdart.dll or delete it, the reinstall/repair stops. I am really really stuck in no mans land unless someone can come up with a workaround so the repair can complete

danjava

I was able to get the file back from another system. I will try your suggestion of using the ctrl key and report back. :-)
Any idea what folder unregmp2.exe belongs in. It is missing on my system, but I can move it from another system if I know where to put it. It is located only in the
windows\servicepackfiles\i386 folder on my good system, but that folder does not yet exist on the system with the problem because I have not reinstalled any servicepacks yet.

danjava

look in c:\windows\inf

Gemarti:

The only place I find the unregmp2.exe on my other two XP Home systems is in the windows|servicepackfiles\i386 folder which does not yet exist on the system with the problem. Are you suggesting I put the unregmp2.exe file in the windows\inf folder??

danjava

The Ctrl + click trick worked.

clicking the ok key until the message went away worked for me as well ! ... thank god for that i was having kittens at the thought of a full format and reinstall ! .
good advice gemarti
these forums are extreamly helpfull . :-)

I have the same problem but with wmplayer.exe (Windows Media Player 8) The Ctrl trick didn't work.

Danjava - I have exactly the same problem .. can't print from IE6 and get the same error msg when try to repair

I get past the message by clicking ok loads of times but doesn't solve my printing problem

Did you manage to solve it with reformatting?

Roger

Rogero:

Yes, I placed the unregmp2.exe file in the windows and windows\system32 folders and then reinstalled
XP. I got the file off of another XP system. It fits onto a floppy okay. MSDART.DLL is looking for
unregmp2.exe , when you place it in those folders it satisfies the requirement and the XP reinstall
continues okay.

Hope this helps

Danjava

Thanks Danjava, most helpful

Rog

Thank you.

I did some looking and I found the unregmp2.exe file listed in a directory listing for a previous version of IE.  It is in a cab file called mplayer2.cab.  I was working with a customer (I am a tech) with this error, and managed to dig up this file.  He said the version of media player he has was "whatever came with windows update" I am thinking he has Media Player 9 installed and that repairing XP is trying to take it back to the old version, thus causing a problem with mismatched .dll files.  I found this same error mentioned on this site, as well http://www.mcse.ms/message297206-2.html

This just happended to me when re-installing WIN XP Pro over itself. From the previous posts, it appears that this is a common error. I waited for about 15 minutes or so and the install restarted and I was able to close the window. I experienced a number of problems (e.g.: couldn't open any Office XP app) after the initial WIN XP reinstall. The solution appears going to Windows Update and installing all the critical patches and updates, especially SP1. I believe that the most current .dll and .exe files pertaining to this problem are installed with SP1. Once SP1 was installed, all my apps -- including Office XP -- worked just fine, although I had to remove my USB 2.0 PCI card from device manager and have it recognized on a restart before a couple of my USB 2.0 peripherals would work. Hope this helps.

I was doing the same thing when "The procedure entry point GetIUMS could not be located" error display showed up. I just took out the CD, cleaned it and restarted the repair process. It worked for me.

According to Pest patrol this is an exploiting pest that could be used to break into a system.  They recommend that you remove it. For more info:-

http://www.pestpatrol.com/pestinfo%5Cu%5Cunregmp2_exe.asp

I also had this problem and there seem to be three "recommended" fixes.  
1. keep hitting ok still it stops appearing.
2. power off and on and wait forthe reinstallation to restart.  It should terminate normally on the second attempt.
3. go and get coffee, make a toasted sandwich, walk the dog etc.  When you come back, the installation will have completed normally, regardless of how you respond to that irritating failure message.

I used solution 2.
Hope this helps somebody. Bet I don't get the points though.

Best regards,
Jo Jenkinson
Tanzania.

Hi All,

Your thread gave me some ideas the other night and with some other collaboration I have come up with an acceptable & hopefully easier solution to this bug.  As you have all mentioned it has to do with XP SP1, Media Player and everyone is trying to repair install from an older non-SP1 disk.  As mentioned above it doesn't have anything to do with lince keys (Cd Keys).  A quick fix is either use a SP1 disk if you can get your hands on one or make it yourself.  There are step by step instructions on Microsoft Website, just pump in "Windows XP Service Pack 1".  To make the integrated install disk bootable you'll have to get a "Bin" file from the net 'XPBOOT.BIN".  I've got it, it is small and can give it to those whom need it.

You can use Nero to burn bootable CD, Have XPBOOT.BIN on floppy and use that as your Boot Image, expert options, No Emulation, Boot Message "Microsoft Corporation", Leave Load Segment of Sectors Alone and Number of Sectors to Load - 4. Leave ISO alone just has to be ISO 9660.  Volume Label "WXPVOL_EN" for XP Corp Edition, others I don't know.  Get rid of the reference to Nero in Application

Bugger I hit the wrong button.  Here is the rest.

Publisher & Data Preparer is MICROSOFT_CORPORATION
BURN:- Disk at Once.

With all that do a repair install and you shouldn't have a drama.  Takes a bit but you now have a XP Disk with SP1 and no more dramas if you need to repair install again.

You can use a different CD KEY with the repair install and it won't matter.

Hope this helps.

Willo

Ctrl worked for me.

hitting shift F10 and typing taskmgr.exe in the commandprompt and stopping the unregmp2.exe process in process list worked for me.. much quicker :)

The shift F10 and taskmgr.exe tip was the coolest ever!  Give Thehealer some points too!

lol I read that somewhere else Oliver so the points dont belong to me :) glad to pass on the info tho. have used it a couple of times successfully now :)

Task Manager!  Hah!  That is impressive!  

Just wondering idley what is going to happen when we have to repair over service pack 2.

JoJ.

Didnt say anything about it being impressive JoJay... it just works better than hitting OK a thousand times or powering PC on and off.. as for Service pack 2.. who knows.. lol we'll cross that bridge when we come to it :D

Jojay,

I just had a client physically unplug their system during a SP2 install, "It was taking too long!" So this exact same situation came up as I tried to reinstall. The only difference is that a SP2 error comes up after you end the unregmp2.exe process. I did the same for this “ok only” error and wala. I've also made a XP Pro with SP2 install CD which I'm pretty sure would have prevented these errors. Don’t forget to order your free SP2 CD from Microsoft:

http://www.microsoft.com/windowsxp/downloads/updates/sp2/cdorder/en_us/default.mspx

achoris

LOL.....the control-click actually worked!!! Thanks.  I thought you guess were full of you know what.  For those of you who use CTRL-CLICK, you need to click it for what seems like minutes.  It will eventually go away.  Be persistent!!!!

Holding down the ctrl key and hitting the ok button a ton of times worked for me.

the healer,
  you, sir, rock!
  a million thanks!
  -prash.

prash... madam actually ;)