- This topic has 11 replies, 3 voices, and was last updated 15 years, 9 months ago by
.
-
Posts
-
I installed Breakaway just fine, but when I try to run it I get the following error:
—————————
WinLicense
—————————
A monitor program has been found running in your system.Please, unload it from memory and restart your program.
—————————
OK
—————————What monitor program? What does that mean? How can I fix it?
Thanks.
Well, it happened to me too, in my case it was RegMon ( a developer’s tool to see changes in the registry ). I might be able to help… can you provide me a list of processes running in your computer?
You can get one by opening a command prompt window, and typing
code :tasklist > C:list.txtEdit: Of course, the list would be saved in C:list.txt 🙂
Hi Klanga!
It’s likely RegMon or FileMon. However, these two programs actually install a driver, and it stays in memory even after you close the program (RegMon or FileMon), so you have to restart your computer afterwards. After that, BA should launch fine.
///Leif
Yep, seems to be that.
It was working fine after rebooting. But I hibernated my PC and when I turned it on again, it started doing that again. Now I’m getting the message like about every 30 seconds. So I’m going to have to reboot again.
Does the full version work like this too?
Edit:
Well, it seemed to have stopped now. I got the following message:—————————
Breakaway
—————————
Error starting audio engine:
Child process not responding
—————————
OK
—————————I uninstalled Breakaway for the moment, I need to use programs like Process Monitor.
Hi Klanga!
I’m working with the WinLicense people right now to resolve the issue. Should be fixed in the next version of Breakaway.
///Leif
Odd. This problem began affecting me for the first time last night. I’m running Vista Ultimate 64 and Breakaway 2 – both completely up to date. The only thing I can think of that I did differently yesterday was to run SysInternals Process Explorer and Process Monitor, but neither are in memory anymore. The problem appeared while my son was using GoogleEarth 5, if that helps (though I’ve not had a problem in the past). I run Vipre Antivirus and Antispyware and Windows Firewall.
Very annoying as I can see no way of recovering Breakaway short of rebooting, which I’m about to do now!
As predicted, a reboot solved the problem. Annoying thing is that I am still in the dark as to what caused it. Before I realized that it was related to Breakaway (I realized this later, after trying to interact with the systray icon and getting the error again), I "freaked" out a bit and disconnected from my network and ran first a quick scan and then a deep scan with my AV/AS. Nothing showed up, so it must have been one of the other apps that I ran yesterday.
Later today I will try to replicate this issue and isolate the program. I’ll post back.
Well… it wasn’t Sysinternals Process Explorer or Process Monitor and it wasn’t Google Earth. I’ve tried running other "stuff" that I ran yesterday that I don’t normally run (Corel PaintShop Pro X2 Ultimate, Magix PhotoDesigner – this has reminded me to uninstall this one!), but no joy. When I came back to the computer, my son was frustrated because GoogleEarth kept taking him to a Google site in Firefox3. All I can think is that some cookie or active-x app was downloaded that WinLicense didn’t like? Of course, as noted above, an AV/AS sweep came up clean and it was a reboot that solved the problem. I wish, now, that I had logged what was active in memory before the reboot.
Darwin, it was Process Explorer. Process Explorer is the latest incarnation of Regmon. Upon startup, it silently loads a kernel mode driver, and when you close the program, this driver stays loaded, with no way to remove it except rebooting.
///Leif
OK – thanks Leif! It happened again last night, after my son had another session with GoogleEarth 5. However, as you note, I had run Process Explorer earlier in the day. What I find odd is that I ran Process Explorer at 8 in the morning and all was well until about 8 pm! Anyway, Process Explorer is now banned from my computer/
Cheers,
Mike
I apologize for the inconvenience. I spent [i]a lot[i] of time trying to find a different solution to this particular problem in the beginning, but in today’s world of "3rd-party-originated try-before-you-buy software solutions" (to use the most polite term possible), it’s one of the things I had to live with.
Best,
///Leif
- You must be logged in to reply to this topic.