@haitch@daWallet Is this normal? I downloaded and runed the run.bat file in the new wallet release and then put the blockchain in db folder on appdata and when i opened the wallet this appened and i closed the Wallet process in task manager but this still at 100% non stop:
I'm doing an upload to google drive and that explain the 8,6Mb that are being sended...
This happened before with me but i've thinked it was the Windows bugs so i googled it and the problem is being solved but this time it's not the same i can feel it... because windows is responding fast in apps that are already opened.
So my question is:
Are you guys trying this in small machines too, or is just my PC that goes to 100% when is finish syncronization with the blockchain(i think...)?
Maybe is just my PC that needs an upgrade... If so sorry for this will?!

@gpedro Check out what is running in "Detalhes" with 100% and kill it. ;)

Probably run.bat is restarting the wallet over and over again... that's why the client uses run_java_autodetect.bat actually. If you want to shut down the process you have to kill "cmd"-process or similar (black icon) first and then the java process.

@daWallet i killed 3 processes of Java Runtime and one cmd.exe and all CPU and RAM usage goes down... I opened the wallet and in the online version it has NRS 1.2.6 and the local says to wait the 10 minutes, usually it's 20-25 so i will wait to see. But BURST software usually with me always have this things! Is it just because its in development, is something with my PC or it happens a lot of times?
P.S.: I'm not complaining but i think that a lot of people has even worst hardware than myself and this things could be a problem... Even worst i think when you are working with androids...

@haitch this current database is for client 1.2.6? client 1.2.6 database file now its is over 3gb , that link for the database is under 2 gb and i know its not for client 1.2.6 this is the issue client 1.2.6 it is not accepting it .
do you know how to change config file nxt-default.properties to allow database ?

Due to current fork issues, i would suggest sync via network currently anyway, otherwise there is a risk of spreading a forked/corrupted blockchain here. But thanks @theapple0 for info, i'm quite sure it will be fixed.