I have installed Bullguard 8.5/8.7 (I don't know which one) on my laptop with windows 7.
After a few minutes the firewall switches off and 3 errors pop up. I can't remember the exact message but something about the firewall can't reach connection to the firewall service. Afterwards i have to manually turn it on again.
The next time I turn my laptop on the same problem occurs.
To further provide advice on the matter, I will kindly ask you to do the following:
First, try to reproduce the error messages. Then, take a screenshot of each one (because they're related to different services), and send them to me as follows:
1. Be sure to have the images of the error messages on the screen. 2. Then press the following key-combination "CTRL" + "Prt Sc" (also written "Print Scr", "Print Screen"). 3. Go to Start > Programs > Accessories > Paint. In the Paint menu please go to Edit > Paste. 4. Next, please save the image in .JPG format. To do this, please click on File > Save as... In the "Save as..." box please look for the .JPG or .JPEG format in the bottom section "Save as type". 5. Then attach the screenshot to your reply email and send it to firstname.lastname@example.org
Secondly, send me a sysdump report:
a. Use the following link to download the Sysdump tool:
I have had windows 7 64bit running for about a week now and if it lets me connect to the internet it takes minutes but this morning it would not connect at all, all I had to close down Bullguard and then restart it and It logged onto instantly.
This can't be a good workaround and I ask you please to fix this problem as I would hate to have to move to Kaspersky.
I was getting startup issues with the firewall where it was causing the network not to start properly. I did get a workaround for this from tech. support, but I don't think it's the 'correct' solution.
The workaround was to set the 'startup type' of the 'BullGuard Firewall Service' to 'Automatic (Delayed Startup)'. This causes the service to wait before starting, meaning that the network is up and running correctly by the time the Firewall starts. This fixed my startup issues for me and may help others having similar issues.
HOWEVER, the 'Delayed Startup' option means it is a full 1 minute and 50 seconds before the Firewall Service starts on my machine. This leaves the PC vulnerable for that time as the Firewall is not running.
I suggested they add service dependencies to the Firewall to allow it to start as soon as the network was up, but tech. support indicated that this is not a good idea as viruses/malware etc. could mess with the dependencies causing the firewall not to start (which is a fair point). However, if a virus can do this, then surely it can do it whether or not the service has dependencies or not?
Anyway, if you are having network issues on Windows boot, give this a try and see if it fixes anything. If it does fix things for you, please let tech. support know, and maybe we can get this startup issues resolved.