Results 1 to 8 of 8

Thread: Procedure Entry Point error after restoring Vista partition

  1. #1
    MrMoose2 Guest

    Procedure Entry Point error after restoring Vista partition

    Hello all,
    I have a dual boot machine with XP and Vista. I attempt to use Ghost to
    backup the two partitions individually. When I restore them, Selecting the
    Vista partition from BootMgr starts Vista, but when I log in, I get the
    following error:

    Title Bar: Rundll32.exe Entry Point Not Found
    Dialog: The procedure entry point SdbGetAppCompatDataSize could not be
    located in the dynamic link library apphelp.dll.

    This is soon followed by other errors and a "Your user profile was not
    loaded correctly"...

    I used BCDedit to look at the BCD tables - they appear as they should. I've
    tried the Vista boot disk to repair startup prolems, no help. I've banged my
    head on the wall for awhile and not made any progress....

    The XP partition (Drive C:) is where the BCD info resides. Vista is drive
    D:. Normally, when Vista boots, it switches these two drive letters making
    Vista C: and XP D:. I'm wondering if that drive letter switching is not
    happening after the Vista partition restore anymore or ?

    Any help would be greatly appreciated. Thanks!


  2. #2
    Rick Rogers Guest

    Re: Procedure Entry Point error after restoring Vista partition

    First, are you using the right version of Ghost? Older ones are not
    compatible with Vista and will destroy the image.

    Second, as to the error message, it means that either a) the library file
    (apphelp.dll) cannot be found where it is expected to be, b) the file is not
    the correct version and the subroutine that rundll32 is trying to load does
    not exist or is not at the correct line in the file or c) the file is
    damaged and the routine cannot be accessed. The problem has nothing to do
    with the boot configuration, it has everything to do with a routine used
    during the user logon. It could be a system routine, or one added by the
    installation of a program or service to the system.

  3. #3
    Pensionada Guest

    Re: Procedure Entry Point error after restoring Vista partition

    Sorry for interfering, but I have exactly the same problem and error
    messages.
    However, I used Acronis TrueImage 11.
    In our situation, we just bought 10 new identical systems: installed
    one system (dual-boot XP and Vista) and made a backup (from Vista) on
    an external disc.
    Then, we restored to a new, blank computer.
    XP works fine, but Vista gives the errors mentioned before.

    Can you please advise what to do, other than re-installing and all its
    applications.

  4. #4
    Pensionada Guest

    Re: Procedure Entry Point error after restoring Vista partition

    Following my previous posting: the problem may have to do with the weird
    behavior of the drive letter as was also reported before.
    The 2nd error message says it cannot load the module at C:\windows\etc.
    However, C is where XP resides, not Vista ....

  5. #5
    Join Date
    Aug 2008
    Posts
    1

    Solution

    I had the same problem and I think my solution will fix it.

    ****PROBLEM****
    ===============

    First off, I have a dual boot of XP and Vista. I first installed XP on drive C: then installed Vista on drive D:. I then imaged my whole hard drive with Acronis True Image Home V11. When I restored the image and try to load Vista, I get the following problem in a dialog.

    Title Bar: Rundll32.exe Entry Point Not Found
    Dialog: The procedure entry point SdbGetAppCompatDataSize could not be
    located in the dynamic link library apphelp.dll.

    ****SOLUTION****
    ================

    - After re-imaging, Log into Vista, and avoid any dialogs that say restart the system.
    - Open "regedit".
    - Go to "KEY_LOCAL_MACHINE\SYSTEM\MountedDevices".
    - Then rename "\DosDevices\D:" to "\DosDevices\CTemp:".
    - Then rename "\DosDevices\C:" to "\DosDevices\D:".
    - Then rename "\DosDevices\CTemp:" to "\DosDevices\C:".
    - Restart system and log back into Vista, it should work now.
    - I found the solution from the following website.

    Basically, what's happening was when you originally had the dual boot system working, both the window systems renamed the primary drive. When you log into XP or Vista, they say their primary is C:, even though Vista's primary physical drive is in D:. Also, if you look into the drive C: when you're in XP or Vista, the system files are related to the loaded OS. However, when you re-image the hard drive with the dual boot, Vista will now say the primary drive is still C:, but if you actually look into C:, it has the XP OS system files, not the Vista's OS system files. So the solution above will correct this problem.

  6. #6
    test100 Guest

    Re: Procedure Entry Point error after restoring Vista partition

    I had the same problem and I think my solution will fix it.

    ****PROBLEM****
    ===============

    First off, I have a dual boot of XP and Vista. I first installed XP on
    drive C: then installed Vista on drive D:. I then imaged my whole hard
    drive with Acronis True Image Home V11. When I restored the image and
    try to load Vista, I get the following problem in a dialog.

    Title Bar: Rundll32.exe Entry Point Not Found
    Dialog: The procedure entry point SdbGetAppCompatDataSize could not be
    located in the dynamic link library apphelp.dll.

    ****SOLUTION****
    ================

    - After re-imaging, Log into Vista, and avoid any dialogs that say
    restart the system.
    - Open "regedit".
    - Go to "KEY_LOCAL_MACHINE\SYSTEM\MountedDevices".
    - Then rename "\DosDevices\D:" to "\DosDevices\CTemp:".
    - Then rename "\DosDevices\C:" to "\DosDevices\D:".
    - Then rename "\DosDevices\CTemp:" to "\DosDevices\C:".
    - Restart system and log back into Vista, it should work now.
    - I found the solution from the following website. ('Vista 64 dual boot
    changing drive letter - Vista Forums'

    Basically, what's happening was when you originally had the dual boot
    system working, both the window systems renamed the primary drive.
    When you log into XP or Vista, they say their primary is C:, even
    though Vista's primary physical drive is in D:. Also, if you look into
    the drive C: when you're in XP or Vista, the system files are related to
    the loaded OS. However, when you re-image the hard drive with the dual
    boot, Vista will now say the primary drive is still C:, but if you
    actually look into C:, it has the XP OS system files, not the Vista's
    OS system files. So the solution above will correct this problem.

  7. #7
    Pensionada Guest

    Re: Procedure Entry Point error after restoring Vista partition

    thank you for your suggestion.

    I guess that my problem was probably slightly different, but I solved
    it using the following steps:

    - Copy NTLDR, NTDETECT and BOOT.INI to the root section of all
    partitions.
    - Using Vistabootpro 3.3:

    - (system bootloader screen) select Vista bootloader; select all
    drives
    - Force install and click Install bootloader.

    Hope that this may help others.

  8. #8
    Join Date
    Feb 2010
    Posts
    1

    Procedure Entry Point error after re installing Windows XP

    I obtained an error reading "The procedure entry point SHRegGetValueW could not be located in the dynamic link library SHLWAPI.dll." while running iesetup.exe. I recently re-installed Windows XP on my system. I created a small partition for my Widows files and it got labeled "C:" The remainder of the hd was labeled "F:"(I have two optical drives that were called D: & E:) I am accustom to C: being the majority of my hd space to be. Will changing the letters help with this error message?? Thanks in advance

Similar Threads

  1. Replies: 1
    Last Post: 29-04-2013, 05:35 PM
  2. Replies: 2
    Last Post: 20-04-2012, 04:30 PM
  3. Replies: 2
    Last Post: 30-03-2012, 03:25 PM
  4. Replies: 4
    Last Post: 16-03-2010, 05:56 PM
  5. Replies: 3
    Last Post: 09-12-2009, 09:15 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •