-
Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.
HELP an old XP User
- Thread starter SirBenn21
- Start date
:angryfir:
Quixoticish
Charter Member
Start Menu
Pick run
Type in "services.msc" (without quotation marks)
Scroll down to "cryptographic services".
Right click on it and select "start".
Also change it from "manual" or "disabled" to "automatic".
Try that and see if it works then.
Pick run
Type in "services.msc" (without quotation marks)
Scroll down to "cryptographic services".
Right click on it and select "start".
Also change it from "manual" or "disabled" to "automatic".
Try that and see if it works then.
H
harleyman
Guest
You can also just redownload and run the latest version.
http://www.microsoft.com/downloads/...FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3
http://www.microsoft.com/downloads/...FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3
Quixoticish
Charter Member
Do you have the windows firewall and security centre enabled? If so kill it, it can cause all sorts of little issues like this and isn't really up to much.
Removed the firewall still with no luck.
H
harleyman
Guest
Well did you try a new download and run it? :isadizzy:
Done and I still get the same error. I've tried to run app "as Administrator".
No Luck.
I swear I'm going back to XP. This just sucks!!!
Ben
falcon409
SOH-CM-2026
What OS are you running?Done and I still get the same error. I've tried to run app "as Administrator". No Luck. I swear I'm going back to XP. This just sucks!!!
Ben
H
harleyman
Guest
Hmmm I thought you were using XP......
You must have vista....
If your install of FSX is new, by reinstalling it maybe DX 9 - 10 will load properly .....
Or perhaps try a FSX repair...
Wish I had more for you there...
You must have vista....
If your install of FSX is new, by reinstalling it maybe DX 9 - 10 will load properly .....
Or perhaps try a FSX repair...
Wish I had more for you there...
Done and I still get the same error. I've tried to run app "as Administrator".
No Luck.
I swear I'm going back to XP. This just sucks!!!
Ben
Bjoern
worst developer ever
Did you use the DirectX web installer?
If yes, try the redistributable package here. it contains all the files and doesn't rely on an internet connection:
http://www.microsoft.com/downloads/...E5-5CE1-4032-A207-C693D210F616&displaylang=en
Works for me (Win 7 RTM).
You could also try this:
http://montanaharkin.net/2008/09/14/spore-creature-creator-and-directx-woes/
http://roundtable.audicracy.com/archives/92 (Illustrated version)
If yes, try the redistributable package here. it contains all the files and doesn't rely on an internet connection:
http://www.microsoft.com/downloads/...E5-5CE1-4032-A207-C693D210F616&displaylang=en
Works for me (Win 7 RTM).
You could also try this:
http://montanaharkin.net/2008/09/14/spore-creature-creator-and-directx-woes/
http://roundtable.audicracy.com/archives/92 (Illustrated version)
Hi
For those of you who are interested how I fixed it.
First I had too
"Check if the HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing registry key is set to 0x63c00. This value is Microsoft's WinTrust policy selection flags, as described here. The 0x40000 flag means "Allow only items in personal trust database" and apparently, this clashes with FSX's ability to allow manual authorization of unrecognized DLLs, telling it instead to never trust anything outside the user's personal trust.
Unsetting this flag (putting it back to its default 0x23c00 value) returns all operations to normal and Flight Simulator X will once again be able to ask the user to designate the PMDG DLL modules as 'Trusted' software."
and then I had to reset my firewall.
It must have been me messing around trying to get Empeck's winch to work.
Thanks again for all the suggestions.
Ben
For those of you who are interested how I fixed it.
First I had too
"Check if the HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing registry key is set to 0x63c00. This value is Microsoft's WinTrust policy selection flags, as described here. The 0x40000 flag means "Allow only items in personal trust database" and apparently, this clashes with FSX's ability to allow manual authorization of unrecognized DLLs, telling it instead to never trust anything outside the user's personal trust.
Unsetting this flag (putting it back to its default 0x23c00 value) returns all operations to normal and Flight Simulator X will once again be able to ask the user to designate the PMDG DLL modules as 'Trusted' software."
and then I had to reset my firewall.
It must have been me messing around trying to get Empeck's winch to work.
Thanks again for all the suggestions.
Ben
H
harleyman
Guest
Man...The things we are willing to undergo just for a nice flight...LOL
Glad you got it sorted out....
Glad you got it sorted out....