Solved Win7 Ultimate x64 SP1 Updates Fail - KB2619339 - KB2729094 - KB976932

[McCaulk]

Hello,

Iv been trying to update my windows installation but have been receiving errors that i don't know how to get past.

The only updates available for me to update (Aside from the Optional Language Packs) are the following.

Security Update for Windows 7 for x64-based Systems (KB2619339)

Update for Windows 7 for x64-based Systems (KB2729094)

Windows 7 Service Pack 1 for x64-based Systems (KB976932)

When i try to update windows starts the update process then in the middle of the update i get this pop up.

*Attachment 1 (Image1)

As soon as i press close on this Windows the Windows update instantly fails

*Attachment 2 (Image2)

I think i have downloaded the System readiness tool and ran it but it goes through the update process and says it finishes then reboots but when i try to update the same 3 updates fail.

Im not sure what to try from here, it's been like this for a while now iv just been putting off the update but now i am trying to update all my drivers and windows to get my 5970 GPU to start rendering my videos in Vegas instead of my i& which takes a lot longer for 1080p videos.

If there is any other information i need to provide please let me know and i will do my best to get everything required.

Thanks
Bob

 

[tom982]

Hello Bob and welcome to the forums

In Method 2 on this page, you'll find instructions on how to run the System Update Readiness Tool.

System Update Readiness Tool fixes Windows Update errors in Windows 8, Windows 7, Windows Vista, Windows Server 2008 R2, and Windows Server 2008

Download and install the tool (save it in a convenient location as we'll have to use it again in the future). After it has completed, copy and paste the contents of its log into your next post please:

C:\Windows\Logs\CBS\CheckSUR.persist.log

Tom

 

[McCaulk]

Hi Tom,

Thanks for the welcoming response.

I have done as you said and here is the information in that file

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 16.0
2012-11-16 18:43

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages
(f)    CBS MUM Missing    0x00000002    servicing\Packages\Package_11_for_KB2729094~31bf3856ad364e35~amd64~~6.1.2.0.mum        
(f)    CBS MUM Missing    0x00000002    servicing\Packages\Package_2_for_KB2729094~31bf3856ad364e35~amd64~~6.1.2.0.mum        
(f)    CBS MUM Missing    0x00000002    servicing\Packages\Package_5_for_KB2729094~31bf3856ad364e35~amd64~~6.1.2.0.mum        
(f)    CBS MUM Missing    0x00000002    servicing\Packages\Package_8_for_KB2729094~31bf3856ad364e35~amd64~~6.1.2.0.mum        
(f)    CBS MUM Missing    0x00000002    servicing\Packages\Package_for_KB2729094_RTM~31bf3856ad364e35~amd64~~6.1.2.0.mum        
(f)    CBS MUM Missing    0x00000002    servicing\Packages\Package_for_KB2729094_SP1~31bf3856ad364e35~amd64~~6.1.2.0.mum        
(f)    CBS MUM Missing    0x00000002    servicing\Packages\Package_for_KB2729094~31bf3856ad364e35~amd64~~6.1.2.0.mum        

Checking Component Store
(f)    CSI Manifest Missing    0x00000002    amd64_246a0ed5323982da8661087635f6326f_31bf3856ad364e35_6.1.7601.17888_none_92c1cf65d9736252.manifest    amd64_246a0ed5323982da8661087635f6326f_31bf3856ad364e35_6.1.7601.17888_none_92c1cf65d9736252    
(f)    CSI Manifest Missing    0x00000002    amd64_52d752a9dca81591dcd0802898f0c419_31bf3856ad364e35_6.1.7601.22045_none_450ba5c595a14f8d.manifest    amd64_52d752a9dca81591dcd0802898f0c419_31bf3856ad364e35_6.1.7601.22045_none_450ba5c595a14f8d    
(f)    CSI Manifest Missing    0x00000002    amd64_aeacabc9ec92a222ead364a20d488811_31bf3856ad364e35_6.1.7601.22045_none_31d7473ad5c4d60e.manifest    amd64_aeacabc9ec92a222ead364a20d488811_31bf3856ad364e35_6.1.7601.22045_none_31d7473ad5c4d60e    
(f)    CSI Manifest Missing    0x00000002    amd64_dae81493f6a681683ed893c05ace4e2e_31bf3856ad364e35_6.1.7600.17057_none_8b6e27ac16c86bcb.manifest    amd64_dae81493f6a681683ed893c05ace4e2e_31bf3856ad364e35_6.1.7600.17057_none_8b6e27ac16c86bcb    
(f)    CSI Manifest Missing    0x00000002    amd64_a9fdfab326cab40b0929eeb50a98c855_31bf3856ad364e35_6.1.7600.21258_none_55cb0dbc97ff03c1.manifest    amd64_a9fdfab326cab40b0929eeb50a98c855_31bf3856ad364e35_6.1.7600.21258_none_55cb0dbc97ff03c1    
(f)    CSI Manifest Missing    0x00000002    amd64_be96d57e1712c10e640e129fae10c02c_31bf3856ad364e35_6.1.7600.21258_none_a0a821e5de18e762.manifest    amd64_be96d57e1712c10e640e129fae10c02c_31bf3856ad364e35_6.1.7600.21258_none_a0a821e5de18e762    
(f)    CSI Manifest Missing    0x00000002    amd64_b9a2e5d4fb8da211612842834dc5f34a_31bf3856ad364e35_6.1.7600.17057_none_e34a7a543876b732.manifest    amd64_b9a2e5d4fb8da211612842834dc5f34a_31bf3856ad364e35_6.1.7600.17057_none_e34a7a543876b732    
(f)    CSI Manifest Missing    0x00000002    amd64_561c7dd1d3c94adbddfb43a73b2711be_31bf3856ad364e35_6.1.7601.17888_none_4ebef4b4f9316921.manifest    amd64_561c7dd1d3c94adbddfb43a73b2711be_31bf3856ad364e35_6.1.7601.17888_none_4ebef4b4f9316921    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-font-truetype-segoeui_31bf3856ad364e35_6.1.7601.22045_none_2f4c144d42117054.manifest    amd64_microsoft-windows-font-truetype-segoeui_31bf3856ad364e35_6.1.7601.22045_none_2f4c144d42117054    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-font-truetype-segoeui_31bf3856ad364e35_6.1.7600.17057_none_2cd3493e2bd3b616.manifest    amd64_microsoft-windows-font-truetype-segoeui_31bf3856ad364e35_6.1.7600.17057_none_2cd3493e2bd3b616    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-g..validatefntcache-03_31bf3856ad364e35_6.1.7601.17888_none_a6ac762931614073.manifest    amd64_microsoft-windows-g..validatefntcache-03_31bf3856ad364e35_6.1.7601.17888_none_a6ac762931614073    
(f)    CSI Manifest Missing    0x00000002    amd64_microsoft-windows-font-truetype-segoeui_31bf3856ad364e35_6.1.7600.21258_none_2d5de83944f06c5e.manifest    amd64_microsoft-windows-font-truetype-segoeui_31bf3856ad364e35_6.1.7600.21258_none_2d5de83944f06c5e    
(f)    CSI Manifest Missing    0x00000002    amd64_microsoft-windows-font-truetype-segoeui_31bf3856ad364e35_6.1.7601.17888_none_2e9a608e29115911.manifest    amd64_microsoft-windows-font-truetype-segoeui_31bf3856ad364e35_6.1.7601.17888_none_2e9a608e29115911    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-g..validatefntcache-03_31bf3856ad364e35_6.1.7600.17057_none_a4e55ed934239d78.manifest    amd64_microsoft-windows-g..validatefntcache-03_31bf3856ad364e35_6.1.7600.17057_none_a4e55ed934239d78    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-g..validatefntcache-03_31bf3856ad364e35_6.1.7600.21258_none_a56ffdd44d4053c0.manifest    amd64_microsoft-windows-g..validatefntcache-03_31bf3856ad364e35_6.1.7600.21258_none_a56ffdd44d4053c0    
(f)    CSI Manifest All Zeros    0x00000000    winsxs\Manifests\amd64_microsoft-windows-g..validatefntcache-03_31bf3856ad364e35_6.1.7601.22045_none_a75e29e84a6157b6.manifest    amd64_microsoft-windows-g..validatefntcache-03_31bf3856ad364e35_6.1.7601.22045_none_a75e29e84a6157b6    

Summary:
Seconds executed: 335
 Found 23 errors
  CSI Manifest Missing Total count: 10
  CSI Manifest All Zeros Total count: 6
  CBS MUM Missing Total count: 7

Unavailable repair files:
    winsxs\manifests\amd64_246a0ed5323982da8661087635f6326f_31bf3856ad364e35_6.1.7601.17888_none_92c1cf65d9736252.manifest
    winsxs\manifests\amd64_52d752a9dca81591dcd0802898f0c419_31bf3856ad364e35_6.1.7601.22045_none_450ba5c595a14f8d.manifest
    winsxs\manifests\amd64_aeacabc9ec92a222ead364a20d488811_31bf3856ad364e35_6.1.7601.22045_none_31d7473ad5c4d60e.manifest
    winsxs\manifests\amd64_dae81493f6a681683ed893c05ace4e2e_31bf3856ad364e35_6.1.7600.17057_none_8b6e27ac16c86bcb.manifest
    winsxs\manifests\amd64_a9fdfab326cab40b0929eeb50a98c855_31bf3856ad364e35_6.1.7600.21258_none_55cb0dbc97ff03c1.manifest
    winsxs\manifests\amd64_be96d57e1712c10e640e129fae10c02c_31bf3856ad364e35_6.1.7600.21258_none_a0a821e5de18e762.manifest
    winsxs\manifests\amd64_b9a2e5d4fb8da211612842834dc5f34a_31bf3856ad364e35_6.1.7600.17057_none_e34a7a543876b732.manifest
    winsxs\manifests\amd64_561c7dd1d3c94adbddfb43a73b2711be_31bf3856ad364e35_6.1.7601.17888_none_4ebef4b4f9316921.manifest
    winsxs\manifests\amd64_microsoft-windows-font-truetype-segoeui_31bf3856ad364e35_6.1.7601.22045_none_2f4c144d42117054.manifest
    winsxs\manifests\amd64_microsoft-windows-font-truetype-segoeui_31bf3856ad364e35_6.1.7600.17057_none_2cd3493e2bd3b616.manifest
    winsxs\manifests\amd64_microsoft-windows-g..validatefntcache-03_31bf3856ad364e35_6.1.7601.17888_none_a6ac762931614073.manifest
    winsxs\manifests\amd64_microsoft-windows-font-truetype-segoeui_31bf3856ad364e35_6.1.7600.21258_none_2d5de83944f06c5e.manifest
    winsxs\manifests\amd64_microsoft-windows-font-truetype-segoeui_31bf3856ad364e35_6.1.7601.17888_none_2e9a608e29115911.manifest
    winsxs\manifests\amd64_microsoft-windows-g..validatefntcache-03_31bf3856ad364e35_6.1.7600.17057_none_a4e55ed934239d78.manifest
    winsxs\manifests\amd64_microsoft-windows-g..validatefntcache-03_31bf3856ad364e35_6.1.7600.21258_none_a56ffdd44d4053c0.manifest
    winsxs\manifests\amd64_microsoft-windows-g..validatefntcache-03_31bf3856ad364e35_6.1.7601.22045_none_a75e29e84a6157b6.manifest
    servicing\packages\Package_11_for_KB2729094~31bf3856ad364e35~amd64~~6.1.2.0.mum
    servicing\packages\Package_2_for_KB2729094~31bf3856ad364e35~amd64~~6.1.2.0.mum
    servicing\packages\Package_5_for_KB2729094~31bf3856ad364e35~amd64~~6.1.2.0.mum
    servicing\packages\Package_8_for_KB2729094~31bf3856ad364e35~amd64~~6.1.2.0.mum
    servicing\packages\Package_for_KB2729094_RTM~31bf3856ad364e35~amd64~~6.1.2.0.mum
    servicing\packages\Package_for_KB2729094_SP1~31bf3856ad364e35~amd64~~6.1.2.0.mum
    servicing\packages\Package_for_KB2729094~31bf3856ad364e35~amd64~~6.1.2.0.mum
    servicing\packages\Package_11_for_KB2729094~31bf3856ad364e35~amd64~~6.1.2.0.cat
    servicing\packages\Package_2_for_KB2729094~31bf3856ad364e35~amd64~~6.1.2.0.cat
    servicing\packages\Package_5_for_KB2729094~31bf3856ad364e35~amd64~~6.1.2.0.cat
    servicing\packages\Package_8_for_KB2729094~31bf3856ad364e35~amd64~~6.1.2.0.cat
    servicing\packages\Package_for_KB2729094_RTM~31bf3856ad364e35~amd64~~6.1.2.0.cat
    servicing\packages\Package_for_KB2729094_SP1~31bf3856ad364e35~amd64~~6.1.2.0.cat
    servicing\packages\Package_for_KB2729094~31bf3856ad364e35~amd64~~6.1.2.0.cat

Thanks for the help
Bob

 

[tom982]

Hi Bob,

No worries. Fortunately for you, your errors are all from the same update and are relatively simple to fix:

Windows Update Package Replacement

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Please download the attached file, Packs.zip and save this to your Desktop.
2. Right-click on the file and select Extract All...
3. Tick the box labelled Show extracted files when complete then click Extract
4. A window will open showing two folders, Manifests and Packages
5. Open the Manifests folder and copy the files into the following folder (if there are any files)
   
   C:\Windows\Temp\CheckSur\Winsxs\Manifests
   
   
6. Open the Packages folder and copy the files into the following folder (if there are any files)
   
   C:\Windows\Temp\CheckSur\Servicing\Packages
   
   
7. Run the System Update Readiness Tool (SURT) again
8. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:
   
   C:\Windows\Logs\CBS\CheckSUR.persist.log

You will probably be shown the error code 0x8024200D after performing this fix, if so, please download and install the update from this link. It must be downloaded using Internet Explorer.

http://www.microsoft.com/en-us/download/details.aspx?id=30566

Tom

 

[McCaulk]

Hi Tom,

Iv downloaded that zip and extracted the contents to the proper folders.
You were correct as after i did this i got the error 0x8024200D, i downloaded the program using internet explorer and installed that and then it rebooted my computer.

Here is the new output for SURT

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 16.0
2012-11-16 20:28

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 1007
 No errors detected

But now there are still 2 updates that i get errors with.

• Security Update for Windows 7 for x64-based Systems (KB2619339)

• Windows 7 Service Pack 1 for x64-based Systems (KB976932)

When the update fails i keep getting this error number 0x8024200D even though i have downloaded and installed (and rebooted) the file in your post about this error.

Thanks again
Bob

 

[tom982]

Hi Bob,

Any 0x8024200D error can be solved by downloading the update from the MS website So all you have to do for these two, is download and install them from here:

Download Security Update for Windows 7 for x64-based Systems (KB2619339) from Official Microsoft Download Center

Download Windows 7 and Windows Server 2008 R2 Service Pack 1 (KB976932) from Official Microsoft Download Center
Download file: windows6.1-KB976932-X64.exe

Tom

 

[McCaulk]

Hey Tom,

Great that's perfect, iv just downloaded and installed those 2 updated successfully. After a reboot i was able to check for new updates and successfully update all the new updates found and now am up to date with everything and it's all working fine.

Iv also updated all my GPU drivers successfully as well as before the Windows updates they were failing.

Thanks again
Much appreciated
Bob

 

[tom982]

Hi Bob,

Glad to hear it! Thanks for posting back the results, and you're most welcome for the help.

Let me know if you have any further issues, but for now I think it's safe to say that this problem has been resolved.

Tom

 

[McCaulk]

I have just marked this thread as solved and left feedback.

Now i can start focusing on the original issue that caused me to fix this issue and that's getting my 5970 to render videos using Vegas

 

[tom982]

I have just marked this thread as solved and left feedback.

Now i can start focusing on the original issue that caused me to fix this issue and that's getting my 5970 to render videos using Vegas

Nice graphics card! I've got a 7850 which I thought was pretty good, yours would blow mine out of the water

Anything I can help with? I'm not all that experienced with Vegas, but I can try.

Tom

 

[McCaulk]

Yeah it's a great card and now that's it's getting older it's also getting cheaper but still a really good card.

As for the Vegas issue im still gonna try the basic troubleshooting steps since i was unable too without upgrading Win7 such as reinstalling everything, redoing all the drivers, and reinstalling OpenCL.

Im rending a lot of HD 1080 video which takes forever when they are over 2 hours long, my i7 920 does a good job but would like to take advantage of my GPU to start helping with this process. Just in the Vegas options it does not allow me to enable GPU acceleration, even if i edit the output template to use OpenCL if available.

Funny thing is also within Vegas if i do the "Check GPU" option is says OpenCL is Available.
So gonna update everything or try a reinstall and see if that helps out.

 

[tom982]

Yeah it's a great card and now that's it's getting older it's also getting cheaper but still a really good card.

As for the Vegas issue im still gonna try the basic troubleshooting steps since i was unable too without upgrading Win7 such as reinstalling everything, redoing all the drivers, and reinstalling OpenCL.

Im rending a lot of HD 1080 video which takes forever when they are over 2 hours long, my i7 920 does a good job but would like to take advantage of my GPU to start helping with this process. Just in the Vegas options it does not allow me to enable GPU acceleration, even if i edit the output template to use OpenCL if available.

Funny thing is also within Vegas if i do the "Check GPU" option is says OpenCL is Available.
So gonna update everything or try a reinstall and see if that helps out.

Yeah, those high end AMD cards are great. I splashed out on a i7 3770k, so I couldn't get a graphics card like that - but my build is fast enough as it is, so I'm not complaining

What version of Catalyst do you have? You need 11.7+ to be able to use GPU acceleration. I'd be surprised if you had drivers that old, but it's worth a try I guess.

Tom

 

[McCaulk]

The i7 3770k sure is a fast, especially with applications that take full control of all the threads. Till i needed to start rendering these videos my CPU would never be more then 20% with my 920

Im using the latest stable release which is 12.10.

I just reinstalled the AMD OpenCL SDK and everything is working now, Vegas see's my GPU's and is using them to render videos. Rendering is going much better now and my CPU is now hovering around 30% instead of 100% during the process as well it going much faster.

 

[tom982]

The i7 3770k sure is a fast, especially with applications that take full control of all the threads. Till i needed to start rendering these videos my CPU would never be more then 20% with my 920

Im using the latest stable release which is 12.10.

I just reinstalled the AMD OpenCL SDK and everything is working now, Vegas see's my GPU's and is using them to render videos. Rendering is going much better now and my CPU is now hovering around 30% instead of 100% during the process as well it going much faster.

Yeah, it hurt my bank balance quite a lot though! lol. It runs quite hot though, even on water. On the maximum setting on IntelBurnTest it gets up to 100C (I stopped it before it did damage) and that's on water :shock:

That's great news, thanks for posting back your solution. I'm a keen skier and bought a helmet camera last year and I plan to do some edits for this season, so it's good to know how I can speed up the process.

 

[McCaulk]

Yeah so did my 5970, i managed to get it off of Craigslist for a good price though and still had warranty and have had no problems with it which is a good thing lol.

I haven't overclocked my CPU but under full load it can get up to 99C with just stock cooling. Though i rarely get up that high, currently idling at 60C on all cores with almost 0 load. I was gonna do water cooling but i initially built this for BitCoin mining and the ROI with water cooling just wasn't worth it.

 

[tom982]

Yeah so did my 5970, i managed to get it off of Craigslist for a good price though and still had warranty and have had no problems with it which is a good thing lol.

I haven't overclocked my CPU but under full load it can get up to 99C with just stock cooling. Though i rarely get up that high, currently idling at 60C on all cores with almost 0 load. I was gonna do water cooling but i initially built this for BitCoin mining and the ROI with water cooling just wasn't worth it.

Oh nice, I had to buy mine new

I keep hearing about BitCoin mining, but I don't actually know a thing about it, any chance you could explain the basics? Like, what's the point?

Tom

 

[McCaulk]

It can actually gets really technical if you want to know the real workings but basics are you download a program that "generates" random numbers again and again and again (millions of times per second depending on your computer speed). Think lottery. In the beginning CPU Mining was great and an i7 920 could generate roughly 20 Million Hashes per second. Though this phased out as you are able to use your GPU to your advantage. The 5970 can generate around 700 Million hashes a second, Much faster then the CPU as well as using a lot less power looking at the Hash rate compared to the power rates. That's not even getting into multi card setups, plus even GPU's are gonna start phasing out as ASIC Cards are getting much better not to mention even less power usage.

So now that your generating hashes there are rules to the network. Two different people will not get the same me, while numbers from 1001 to 2000 belongs to you. If the random number/hash matches a "pattern", it is accepted. If it doesn't match the "pattern", it is rejected. For a very simplified example, if the "pattern" says we accept only even numbers, then ~50% of the random numbers will "win lottery" and 50% will miss. If the pattern was so easy to match, I can simply generate the numbers 2, 4, 6, 8... and get a 100% hit rate. Apparently in the real case, even the simplest "pattern" is so hard to match that we can't simply work backwards and try to derive a number that will match the "pattern". The only way to get a number that will match the "pattern" is though trial-and-error, which is why its exactly like a lottery. Don;t forget these are long hashes and not just single digit number.



If the pattern is easy to match, we will get many hits. If the pattern is hard to match, we will get lesser hits. The pattern changes every certain amount of hits to ensure that we get roughly 1 hit every Certain amount of time. If we hit too quickly, we get a harder pattern to match for the next block so that it will take longer. If we hit too slowly, we get an easier pattern to match so the next block will be faster. This is why CPU and GPU is becoming more and more useless with bitcoin mining as when ever one was using CPU's the "pattern" (difficulty rate) was easier but when a lots of GPU mining started happening the "pattern" got harder to ensure that bitcoins could not be generated too fast. The thing with this is with ever new method to hash faster the older methods become more and more useless as a CPU mining at only 20 Million Hashes per seconds (Mhash) is no longer profitable having such a high difficulty rate due to the global hashing speed increasing. Now with the new ASIC Cards coming out it will be possible to have 1 rig hashing at a speed of 1'500 GHash (1500000 Million compared to high end CPU 20Millon) on only 1250 Watts of power. You can see that the difficulty rate will probably dramatically increase once these things hit the market to compensate for the large increase of hashing speeds to make sure that the network stays stable.


Something like that

 

[tom982]

Wow, thanks for the explanation! Who is paying for all of this though? And why do they want these hashes? It seems too good to be true to be honest!

Tom

 

[McCaulk]

That is probably the biggest controversial issue with BitCoins but also one of the reasons behind it. Bitcoins theoretically have no value what so ever, Bitcoins are a fully digital P2P currency not governed by any parties. The rules of the network are put in place to keep the network stable over time. This includes that the block value will decrease probably some time soon from the current value of 50BTC per block down to 25BTC per successful hashed block. This will be the first time this event is going to happen for bitcoins since it was started but it will not be the last.

There is a maximum possible number of 21 Million Bitcoins that would ever be aloud to be created and this is to ensure that BitCoins can last. Every "x" amount of time or solved blocked (not exactly sure) the value per block decreases the current and starting point is 50BTC but this will be lowered to 25BTC then years after this it will again be lowered to 12.5, then to 6.25, and so on. Also why Bitcoin numbers go into decimals as in the event that the price per bitcoin is too large for normal purchasing or currency trading transactions could start taking place at the first decimal value.

But there is no company behind BitCoins giving out this money, it is just the trust in the BitCoin system/network and the need or want for a free currency not governed by a third party. Which in itself does have many advantages.

Another things with BitCoins is the Value can change rather quickly. People have been theorizing on what they think will happen when the block value decreases for the first time to 25BTC. Will the Difficulty rate get dramatically easier as the time per successful block will take twice as long, will the value increase as they might be twice as hard to generate ? Many possibility but only time will really tell.

I definitely took advantage of GPU mining when it was hot, if you didn't mind paying a transfer commission it was relatively easy to transfer BitCoins into simple paypal. But you could also setup P2P exchanges if you wanted to get a better deal but have to find an individual to sell to. With 1BTC = 11USD (Constantly changing) i managed to pay myself back for my whole computer. But i personally think were getting to the end of the GPU stage.

 

[tom982]

That is probably the biggest controversial issue with BitCoins but also one of the reasons behind it. Bitcoins theoretically have no value what so ever, Bitcoins are a fully digital P2P currency not governed by any parties. The rules of the network are put in place to keep the network stable over time. This includes that the block value will decrease probably some time soon from the current value of 50BTC per block down to 25BTC per successful hashed block. This will be the first time this event is going to happen for bitcoins since it was started but it will not be the last.

There is a maximum possible number of 21 Million Bitcoins that would ever be aloud to be created and this is to ensure that BitCoins can last. Every "x" amount of time or solved blocked (not exactly sure) the value per block decreases the current and starting point is 50BTC but this will be lowered to 25BTC then years after this it will again be lowered to 12.5, then to 6.25, and so on. Also why Bitcoin numbers go into decimals as in the event that the price per bitcoin is too large for normal purchasing or currency trading transactions could start taking place at the first decimal value.

But there is no company behind BitCoins giving out this money, it is just the trust in the BitCoin system/network and the need or want for a free currency not governed by a third party. Which in itself does have many advantages.

Another things with BitCoins is the Value can change rather quickly. People have been theorizing on what they think will happen when the block value decreases for the first time to 25BTC. Will the Difficulty rate get dramatically easier as the time per successful block will take twice as long, will the value increase as they might be twice as hard to generate ? Many possibility but only time will really tell.

I definitely took advantage of GPU mining when it was hot, if you didn't mind paying a transfer commission it was relatively easy to transfer BitCoins into simple paypal. But you could also setup P2P exchanges if you wanted to get a better deal but have to find an individual to sell to. With 1BTC = 11USD (Constantly changing) i managed to pay myself back for my whole computer. But i personally think were getting to the end of the GPU stage.

Thanks again for the detailed explanation. My internet isn't exactly slow (see below) and it's taking forever to sync to the network. I've got roughly 6k blocks left to download and it's going at less than one per second. Looks like this could take a while!