Encore Pro install reboot loop question

Pugsy wrote:Thank you for sharing John.
Now I will point the other person to this thread. Something for her to try.
I will also try to remember this and bookmark this thread. I guess I jinxed you by saying you shouldn't have any problem. Question for you, is the Whyreboot thing easy to do and follow?

One other person has some issues but they are user related to unsure if I can help him. One of those things I could resolve I am sure if I was sitting in front of his computer but he is too far away for house call and I don't do the remote thingy. Don't want that responsibility.

The Whyreboot thing was easy to use, but interpreting the info could be tricky depending on the user. Most of the output was garbage, but there was enough there to figure out what it was. If you are going to have the other person try it, you will want them to copy the output to send to you, or do a screenshot. Fortunately the fix for me was easy enough. Thanks for your help!

John M. Browning wrote:If you are going to have the other person try it, you will want them to copy the output to send to you, or do a screenshot. Fortunately the fix for me was easy enough.

Oh crap, me look at it? Well, I suppose it couldn't be any worse than doing hijackthis logs and those other malware removal logs... But I am so rusty..

Actually I think she has a friend that is fairly computer literate in areas she feels weak in.

I have emailed her about this possible solution. I am wondering if the failed uninstall of EncorePro 1.8 has messed up things.
Course it could be anything else also that left bits and pieces. Encore Pro uninstall is terribly dirty uninstall. I ran into that with EP 2.4 and I messed up the first install.

Pugsy wrote: Encore Pro uninstall is terribly dirty uninstall.

Oh thanks! NOW you tell me!


lol

In case this could help somebody:

My EncorePro2 (version 2..4.12.2) was working properly but all the sudden today while trying to open it I received the message "Could not check the data base version" (data base version 2.3.1.46). The computer haven't been shut down and I had used EnocrePro2 two days ago. I have Win7 64bits.

To fix the problem I opened the SQL Server Configuration Manager. The SQL Server (ENCOREPRO2) appeared as Stopped, I started it and tried to open again EncorePro2, it worked.

Moral of the story: before unistalling the SQL data base check if it is started, this will save you some troubles.

I was directed to this thread today because I am not having this problem. I have tried everything that has been suggested here with no luck. I have a feeling that someplce there is an old instance to an old sql server and that is why I am getting the reboot.

Anyone else have any ideas?

I am reposting this work around here because I had posted in here at the suggestion of someone else. I did figure out the workaround for this so give it a try but read it all first.


I got this to install under Windows 7 64 and under a virtual xp on the same machine. This is what I had to do.

First if you have never done anything in the registry then don't mess with this, you delete or change the wrong thing and you mess up your computer big time. Second read through the whole thing first then try it.
This is the only way that I have found to install this. The problem is with the sql server install.

I clicked start, run then typed in regedit then finding the key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager" then deleting the value of "PendingFileRenameOperations". Then you close the editor and do not reboot rather run the installer again.

Their could also be a couple other places that files are hiding.


Check the below registry keys for any values for reboot.


HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnceEx
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServicesOnce
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce


The same as before, close the registry editor and run the install program. Do not reboot the computer until after you have installed the software or temp files will be placed back and cause the same problem.