Error accessing the system registry on VISTA
Ton
known:
http://support.microsoft.com/default.aspx/kb/269383
the solution is there but allthough I exactly know which key is giving me
the trouble (not because of crystal reports, but because of an update of
adobe). The thing is I can't modify the security settings. And the workaround
described to start the cmd-prompt as a system account task is not working. On
vista this is not possible.
So my exact question is:
How can I modify the security of a (typelib) key in the registry. !!!
Please help. It allready was a pain in the ass to install VS2005 and VB6 on
vista and after several months I've troubles again.
Thanx
Ton
Ralph
"Ton" <T...@discussions.microsoft.com> wrote in message
news:D6B4B4F0-F75B-4F57...@microsoft.com...
Have you tried logging in as an Administrator in Safe Mode?
-ralph
Ton
In stead of trying to add users to the security I first clicked on the
advanced button, where I clicked on the owner tab. There was no owner yet. It
was possitble tot add the administrator. I closed this window and then....
I could simply add the administrator account for full control! Closing this
window and opening it again, showed me that my normal account could read the
keys.
The problem was not over yet. Because the regmon utiliy showed another key
with the same problem. But after I've fixed about 8 key's, I could set my
references in my VB project and the problem was solved.
The reason an update of adobe about a week ago had damaged my registry.
Ralph
> I have not, but just found the solution:
> In stead of trying to add users to the security I first clicked on the
> advanced button, where I clicked on the owner tab. There was no owner yet.
It
> was possitble tot add the administrator. I closed this window and then....
>
> I could simply add the administrator account for full control! Closing
this
> window and opening it again, showed me that my normal account could read
the
> keys.
>
> The problem was not over yet. Because the regmon utiliy showed another key
> with the same problem. But after I've fixed about 8 key's, I could set my
> references in my VB project and the problem was solved.
> The reason an update of adobe about a week ago had damaged my registry.
>
> "Ralph" wrote:
LOL
Amazing how obviously simple it is once you know the answer. <g>
Thank you very much for reporting back and sharing what you found out.
-ralph