Hi there.
I was trying to repackage Naturally Speaking version 9 and
I was successfully able to create an msi.
The problem is though, when I run the msi and it reaches the stage
where it is writing registry data, the installation interrupts with an
Error 1406 stating that it cannot write a particular key to the registry.
I am absolutely stumped as I am logged in as administrator and I checked the
permissions associated with the parent key that the msi is trying to write to,
and the administrator and system accounts have full control.
Interestingly enough, when I try to create a new key under another key (Say its called X)
I cannot do this.XP gives me an error saying "Error writing to the registry."
Also it is worth mentioning that I am running the msi on a clean build of XP.
I dont get it, has anyone had this problem before?
Any input will be very welcome!
Thank you all,
Best regards.
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Remember that permissions in the registry are pretty tricky.

Just because the Allow box is checked doesn't mean you are allowed.

Open the permissions for one of the keys you are trying to write to. Check the "Everyone" member, make sure that the special permissions or deny is not checked(a grayed out box signifies the property is inherted, go to the parent and check). If special permissions is checked then click advanced and see if you can erase any "extra" permissions - I would also check the SYSTEM entry.

My guess is that if that key is not directly been altered to block a user group, which just happens to include the users you are attempting the change with, then the key is inherting it from a parent key.

In the registry, if you are denied in any context an allow doesn't matter - the DENY is king.

If you want to make sure - open the permissions folder - click advanced, uncheck the "Inherit from parent.... " box, select all the permissions entries and click remove and then apply, NOT OK - DON'T CLOSE THE WINDOW. Click Add, type Everyone for the object name to select, then click check names. Click ok - choose Full Control, click OK. Do this for each key that is causing a problem... if it works after this, at least you know that you have a permissions issue and it's not something else disguising itself as one.

Hope this helps.
Answered 01/29/2007 by: gmorgan618
Blue Belt

Please log in to comment
Thanks very much for your help.
I'll give this a go and report back.
Thanks again and best regards.
Answered 01/30/2007 by: shamrock
Orange Belt

Please log in to comment
What key is your MSI failing to write to?
The vendor supplies an MSI and by repackaging their installation (if that is what you are doing), you may experience very strange behaviour (kinda like what you are experiencing)...
Answered 01/30/2007 by: AB
Purple Belt

Please log in to comment
You are right.
There is an msi supplied but the thing is when I do an admin
install to a network location and click the msi,
its says "A required file (...\setup.cab) is missing or damaged.Setup cannot continue installation and will exit now".
The setup.cab is located on the installation cd.
I set the cd drive as my active location and ran the vandor supplied msi with "msiexec /a vendormsi.msi"
and the admin installation completes successfully, yet i get the above error when i double click the msi.
I might try to edit the msi and add the setup.cab from the cd.
Thanks for the help.
Answered 01/30/2007 by: shamrock
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity