Next time I've went trying to load hives with wb all worked perfectly fine on other test folders, except the one where I was originally testing with UAC enabled.
The link you've provided was most usefull to learn:
Vista includes a new notion of what were originally called "Mandatory Integrity Controls" but eventually became "Windows Integrity Controls." Under WIC, every object that have permission can also have a label that identifies its "integrity level." There are six integrity levels, from highest trustworthiness to lowest:
* Trusted Installer
* System (operating system processes)
* High (administrators)
* Medium (non-administrators)
* Low (temporary Internet files)
* Untrusted
Files and folders have integrity levels, as do users and processes. What good are these "trustworthiness levels?" Well, they act as a kind of second level of Windows permissions. When a lower-integrity user tries to modify a higher-integrity object, then Windows integrity controls blocks the modification attempt, and blocks it even if the object's permissions list contains a "full control" permission for that user. It is, thus, a sort of set of uber-permissions, albeit a simple one.
And a solution:
1. Open gpedit.msc
2. Navigate to Computer Configuration / Windows Settings / Local Policies / User Rights Assignment
3. In the right-hand pane, you'll see an entry "Modify an object label;" open it
4. By default, there are no user accounts listing with this privilege. Add your user account.
5. Close the Group Policy Editor
6. Log off, then back on to finish getting the new privilege on your logon token.
A very big THANKS for the help, I'm sure many others will get stuck on this part too..