Topic: No blocks downloaded - MS Security Essentials users please read (Read 49494 times)
As far as I know they fixed this one. I've had no trouble with MSSE in regards to the troubles listed in this thread.
December 06, 2013, 10:03:08 AM
Is this still a problem with the current version?
Mine gets blocks as well albeit pretty slow. I am going to try the exclusion and see if that helps speed it up.
I've been running bitcoin with microsoft security essentials for a long while now, and it has always been able to get blocks. Port forwarding on my router was simple, it supports UPnP, which I like using. I discovered that running bitcoin caused MSSE to grind away at the hard drive excessively, so I added the bitcoin data directory to the exceptions list, and it calmed down right away. I just now added the bitcoin application to the excluded processes list, just in case that might become a problem some day. I'm running the newest version of Bitcoin, so, maybe that's why it didn't have trouble getting blocks, I dunno.
Here is a guide on how to exclude a process:
http://maximumpcguides.com/windows-7/set-microsoft-security-essentials-to-exclude-a-process/
You need to exclude bitcoin.exe from live protection.
http://maximumpcguides.com/windows-7/set-microsoft-security-essentials-to-exclude-a-process/
You need to exclude bitcoin.exe from live protection.
Clear and easy.
Thank you for this, I feel dumb for not figuring it out myself...haha.
it's fun reading old posts sometimes...
January 25, 2011, 06:45:22 PM
I am not sure if this still applies. I use security essentials on all machines (Win7, Win2k8) here without any special exceptions and have no problems whatsoever.
Just make sure you forward port 8333 on your router to the machine that hosts your bitcoin wallet.
Just make sure you forward port 8333 on your router to the machine that hosts your bitcoin wallet.
January 21, 2011, 07:24:48 PM
Hello,
I have a very similar problem but I am not using Microsoft Security Essentials. In my case I have a Western Digital external backup hard drive and their program WD Smartware is hogging the cpu time. That program is very 'dumb' and there are no configuration options that I am aware of to make it less aggressive. In fact, right now I cannot even open the user interface. There is an option to pause backup until computer is idle, but that has been checked since day 1.
My Bitcoin usually has 30 or more connections open, but the block count has been frozen at 99789 since sometime in December 2010. The one transaction has 6847 confirmations, also unchanged since December. There are some files being updated in the wallet, however.
I am running Windows xp sp3.
I have not yet tried shutting down WD Smartware for an extended period, but that will probably be my next experiment.
Has anyone else had a similar variation of this problem?
David
I have a very similar problem but I am not using Microsoft Security Essentials. In my case I have a Western Digital external backup hard drive and their program WD Smartware is hogging the cpu time. That program is very 'dumb' and there are no configuration options that I am aware of to make it less aggressive. In fact, right now I cannot even open the user interface. There is an option to pause backup until computer is idle, but that has been checked since day 1.
My Bitcoin usually has 30 or more connections open, but the block count has been frozen at 99789 since sometime in December 2010. The one transaction has 6847 confirmations, also unchanged since December. There are some files being updated in the wallet, however.
I am running Windows xp sp3.
I have not yet tried shutting down WD Smartware for an extended period, but that will probably be my next experiment.
Has anyone else had a similar variation of this problem?
David
August 16, 2010, 07:56:37 PM
Well, I asked him to add bitcoin.exe to the "Excluded processes" list of Microsoft Security Essentials, and block downloads took off for him after that.
This is the EXACT same experience that I had. With MSFT Forefront installed (which I just did recently), I noticed that Bitcoin completely stopped downloading blocks. The moment I added it to the list of *excluded* processes, then immediately blocks began to download again.
Very odd.
Okay, I solved the problem. The solution was in https://bitcointalksearch.org/topic/win32-cpu-cycles-vs-live-protection-engines-35.
This worked for me too! Thanks.
Microsoft Security Essentials was locking up the bitcoin.exe process. The thread with the solution has several responses from other people running various editions of Windows. The problem may extend to other virus protection software. You just have to exclude the bitcoin.exe process from its scan, and it's probably healthy to add the block database files to the exclude list as well. Of course, this opens the excluded files up to infection, but it's a risk you'll have to take until another solution can be found.
Here is a guide on how to exclude a process:
http://maximumpcguides.com/windows-7/set-microsoft-security-essentials-to-exclude-a-process/
You need to exclude bitcoin.exe from live protection.
http://maximumpcguides.com/windows-7/set-microsoft-security-essentials-to-exclude-a-process/
You need to exclude bitcoin.exe from live protection.
Well, I asked him to add bitcoin.exe to the "Excluded processes" list of Microsoft Security Essentials, and block downloads took off for him after that.
So that was responsible for keeping blocks from downloading?
The link: "Win32 CPU Cycles vs 'Live Protection' Engines"
For BitcoinFX, Live Protection was keeping it from getting CPU for generating coins. You said your friend was getting 1400-1600 khash/s, so it was getting CPU. I guess Live Protection must have been blocking some other part of the program then?
The link: "Win32 CPU Cycles vs 'Live Protection' Engines"
For BitcoinFX, Live Protection was keeping it from getting CPU for generating coins. You said your friend was getting 1400-1600 khash/s, so it was getting CPU. I guess Live Protection must have been blocking some other part of the program then?
Okay, I solved the problem. The solution was in https://bitcointalksearch.org/topic/win32-cpu-cycles-vs-live-protection-engines-35.
Yea, possibly a full disk, or a failing disk... It's odd that even with a dedicated connection within your LAN it took that long to get that number of blocks. My 100 Mbps router funneled them from one of my PCs to another in less than 15 minutes, at the 65K+ blocks it needed.
Maybe a flakey router or internet connection? Might be worthwhile to do a speed test, or research Microsoft Security Essentials to make sure it's not toying with Bitcoin's ability to build the block list in some other way... not too familiar with Microsoft products I'm afraid.
Maybe a flakey router or internet connection? Might be worthwhile to do a speed test, or research Microsoft Security Essentials to make sure it's not toying with Bitcoin's ability to build the block list in some other way... not too familiar with Microsoft products I'm afraid.
Maybe, the hdd is full?
I think I read somewhere that if he has any connections, he is connecting to the IRC channel just fine... I think you're correct on the 8 connection limit without having port 8333 forwarded.
My thinking was that the static IP -addnode would help by providing a dedicated download source. If that still doesn't work well then I'd guess that laszlo has hit the nail on the head, and the constant full-rewrite of the file is to blame.
My thinking was that the static IP -addnode would help by providing a dedicated download source. If that still doesn't work well then I'd guess that laszlo has hit the nail on the head, and the constant full-rewrite of the file is to blame.
Oh, right. Missed that he had 40 connections.
But 0 blocks downloaded?
My macmini is currently downloading blocks. It is up to 38xxx after about 4 hours. That is with two dedicated sources on the same lan plus another 6 it discovered out on the 'net. (It is a 2009 model with 4gb of ram using only a 150GB partition of a 500GB, 7200rpm, 2.5" drive, running the 0.30 .zip'd version as a -server.)
The old macmini drive is in an atom D510 system and is a very slow hard disk. It took a long time (18+hours) to download the blocks even with a dedicated source. But even then it did not stay at 0 blocks for more than a minute or so.
I wonder how much downloading to a ramdisk would speed it up...
I think I read somewhere that if he has any connections, he is connecting to the IRC channel just fine... I think you're correct on the 8 connection limit without having port 8333 forwarded.
My thinking was that the static IP -addnode would help by providing a dedicated download source. If that still doesn't work well then I'd guess that laszlo has hit the nail on the head, and the constant full-rewrite of the file is to blame.
My thinking was that the static IP -addnode would help by providing a dedicated download source. If that still doesn't work well then I'd guess that laszlo has hit the nail on the head, and the constant full-rewrite of the file is to blame.
Well, I don't have port 8333 open, but I was able to download all the blocks. (I don't use a firewall, though.)
I'll ask him to get rights to the firewall and check what it does with port 8333 connections. His port 8333 is open, but the firewall may be messing with it.
I'll ask him to get rights to the firewall and check what it does with port 8333 connections. His port 8333 is open, but the firewall may be messing with it.
The static IP using addnode will probably work.
However the software is designed to bootstrap using IRC. Probably connecting out to the IRC server is being blocked either by Microsoft or his Linux firewall. Without IRC his system is unable to discover other nodes.
IRC has nothing to do with port 8333, but most likely the Linux firewall is blocking incoming port 8333, so bitcoin will need to establish outgoing connections to other systems with a 8333 open for incoming connections. Without opening incoming 8333 the max connections will be limited to 8 (I think).
However the software is designed to bootstrap using IRC. Probably connecting out to the IRC server is being blocked either by Microsoft or his Linux firewall. Without IRC his system is unable to discover other nodes.
IRC has nothing to do with port 8333, but most likely the Linux firewall is blocking incoming port 8333, so bitcoin will need to establish outgoing connections to other systems with a 8333 open for incoming connections. Without opening incoming 8333 the max connections will be limited to 8 (I think).
This seems like a commonly reported problem now - something to do with the block downloading being really slow. It may be related to the excessive amount of disk I/O that is generated during the initial download. The database file is flushed to disk every time a block is added so this is being really slow for some people. I think we can probably fix this up now that we know about it.. I for one didn't do much testing without having all the blocks, so it never occurred to me to try this under different systems.
Might need to have him start it with -addnode=x.x.x.x, where x.x.x.x is someone's static IP. Hopefully someone should be able to share theirs for that purpose... if that's the issue, of course. :-) I don't know for sure though.
I got my friend to download and try Bitcoin out. I sent him one coin, but he hasn't received it. For some reason, his client isn't downloading any blocks. He turned on "Generate Coins" the minute he started the program for the first time. His speeds were in the 1400-1600 khash/s range, and he had 3 blocks. He generated 50 coins which will mature in another 100 blocks or so. He has around 40 connections.
To my knowledge, his coins will be invalid because none of the other nodes will accept his blocks. And, since he hasn't downloaded any blocks, he won't receive the one Bitcoin I sent him.
He uses Microsoft Security Essentials, but has added Bitcoin to its unblock list. He does have port 8333 open, but has a Linux network firewall. (He doesn't have the rights to access the firewall.)
What could be the problem?
To my knowledge, his coins will be invalid because none of the other nodes will accept his blocks. And, since he hasn't downloaded any blocks, he won't receive the one Bitcoin I sent him.
He uses Microsoft Security Essentials, but has added Bitcoin to its unblock list. He does have port 8333 open, but has a Linux network firewall. (He doesn't have the rights to access the firewall.)
What could be the problem?
Jump to: