ireboot stopped working

Zombo

New Member
#1
I have easybcd set up in a dual boot configuration. Windows 7 ultimate sp1 is my primary os and Windows vista home premium sp2 is my secondary os. I installed ireboot on windows 7 and it was so cool at first. I could switch from 7 to vista flawlessly. Then I installed ireboot on windows vista so I could switch back to 7 without trouble. It worked great for a while but now, whenever i try to access ireboot in 7 I get this error message:
"ireboot has stopped working, windows is collecting more information about the problem"
If I am in vista, ireboot still works perfectly. Thank you for easybcd and ireboot, I really like them
 

Ex_Brit

If you're going through hell, keep going.
Staff member
#2
Try uninstalling the non-working iReboot and then reinstall the latest from here: iReboot
It wont work properly until after a reboot.
 

Zombo

New Member
#3
Thank you for offering assistance with my problem. I did as you recommended and uninstalled my copy of ireboot and then did a fresh install of the one from the link you provided, after installing, I then rebooted but it still gives me the same error.
I don't know if this matters or not but each of my operating systems are on a separate hard drive. Windows 7 is on C drive while Vista is on D. Also, I am sorry it took me so long to reply. I have been away on the road working.
 

Ex_Brit

If you're going through hell, keep going.
Staff member
#4
Install EasyBCD on the system drive that provides the boot menu, I assume Vista.. Make sure the OS's are setup in EasyBCD properly as per drive letters etc. Reboot and see if things work better.
EasyBCD is free for personal use: EasyBCD
 

Zombo

New Member
#5
I already had EasyBCD installed on the windows 7 drive. I guess it is the one that provides the boot menu. Originally this pc came with vista but I did a fresh install of windows 7 because microsoft is abandoning support of vista. After I got windows 7 installed and it was the only OS on my computer, I decided to re install windows vista from a backup. I installed it to its own drive. So how do I know for sure which OS provides the boot menu? I made sure all of the OS settings are setup right in EasyBCD as per drive letters and so forth but I am still getting the same error.
I noticed online a lot of different people have had the same problems with basically the same error message as I get with iReboot, except they are having these problems with programs other than iReboot.
Here is a detailed list of what appears in the error box:
"Files that help describe the problem:
C:\Users\Walker\AppData\Local\Temp\WERDC59.tmp.WERInternalMetadata.xml
C:\Users\Walker\AppData\Local\Temp\WERDFD4.tmp.appcompat.txt
C:\Users\Walker\AppData\Local\Temp\WERE071.tmp.mdmp"
 

Ex_Brit

If you're going through hell, keep going.
Staff member
#6
You'll see where the boot menu is in Administrative Tools > Computer Management > Disk Management It'll say "System" in one of the descriptions.
I'm asking for help as I'm now out of my depth knowledge-wise.
 

Ex_Brit

If you're going through hell, keep going.
Staff member
#8
You're welcome.
 

mqudsi

Mostly Harmless
Staff member
#9
It might be a BCD configuration that iReboot isn't able to handle correctly - can you please post the full output of EasyBCD's detailed mode here?
 

Zombo

New Member
#10
mqudsi, thank you for helping here is the full output from detailed mode:

Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=C:
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {753301a4-930f-11e6-9fb9-eb64f538c037}
resumeobject {753301a3-930f-11e6-9fb9-eb64f538c037}
displayorder {753301a4-930f-11e6-9fb9-eb64f538c037}
{41018aaf-98d7-11e6-8f98-001d098d6b1a}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30
displaybootmenu Yes

Windows Boot Loader
-------------------
identifier {753301a4-930f-11e6-9fb9-eb64f538c037}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {753301a5-930f-11e6-9fb9-eb64f538c037}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {753301a3-930f-11e6-9fb9-eb64f538c037}
nx OptIn
pae Default
sos No
debug No

Windows Boot Loader
-------------------
identifier {41018aaf-98d7-11e6-8f98-001d098d6b1a}
device partition=D:
path \Windows\system32\winload.exe
description Windows vista
locale en-US
osdevice partition=D:
systemroot \Windows
resumeobject {96b1bdd7-98d7-11e6-a489-806e6f6e6963}
 

mqudsi

Mostly Harmless
Staff member
#11
Oh, and can you please try deleting the NeoSmart_Technologies folder in C:\Users\YOUR_USER_NAME\AppData\Local\NeoSmart_Technologies and seeing if that helps?
 

Zombo

New Member
#12
Wow thank you! That was it! I just deleted the folder and it works again. Thank you for helping me get to the bottom of this :smile:
 

Ex_Brit

If you're going through hell, keep going.
Staff member
#13
@Zombo Great, glad to hear it's fixed for you now.
@mqudsi thanks for the help :smile:
 

mqudsi

Mostly Harmless
Staff member
#14
It's a bug in Microsoft's .NET where the settings file can get corrupted; I worked around this in EasyBCD and I should probably do the same for iReboot.
Glad it worked, and sorry for the delay in stepping in! You can thank @Ex_Brit for making sure I saw this.
 

Ex_Brit

If you're going through hell, keep going.
Staff member
#16
:blush: