# PropertySet Load from Registry failing
**URL:** https://www.finalbuilder.com/forums/t/propertyset-load-from-registry-failing/3683
**Category:** Bugs
**Created:** [February 11, 2018, 2:29am UTC](https://www.finalbuilder.com/forums/t/propertyset-load-from-registry-failing/3683 "2018-02-11T02:29:00Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@mikef74](https://www.finalbuilder.com/forums/u/mikef74)
#### Post date: [February 11, 2018, 2:29am UTC](https://www.finalbuilder.com/forums/t/propertyset-load-from-registry-failing/3683/1 "2018-02-11T02:29:00Z")
I can save a property set to the registry just fine, but cannot load from the same registry location. While I have not verified the cause, I suspect it is because one of my keys has spaces in it.
This is 8.0.0.2338, the latest released version available via Help-\> Check For Updates.
---
### Author:  [@mikef74](https://www.finalbuilder.com/forums/u/mikef74)
#### Post date: [February 11, 2018, 3:24am UTC](https://www.finalbuilder.com/forums/t/propertyset-load-from-registry-failing/3683/2 "2018-02-11T03:24:33Z")
After more investigation, it’s not the spaces. Even though the Load and Save registry have the same key entered, it looks like the save is doubling-up on the WOW6432Node and thus putting my data in the wrong spot. I am going to remove WOW6432node only from my Save action and see what happens.
---
### Author:  [@mikef74](https://www.finalbuilder.com/forums/u/mikef74)
#### Post date: [February 11, 2018, 3:31am UTC](https://www.finalbuilder.com/forums/t/propertyset-load-from-registry-failing/3683/3 "2018-02-11T03:31:51Z")
Yup, that was the solution, removing my single WOW6432Node saved it in the expected location.