Direct 3D 9.0 is missing on Windows 7 logon screen... how to enable?

[Radical924]

Okay so I followed this tutorial: Change Windows 7 Logon/Logoff Screensaver! and I know this ia a common problem but anyways I receive an error that Direct 3D 9.0 is missing. Keep in mind this is for the windows 7 logon screen... How do I enable this so I can have my own custom screensavers at the logon screen???

Also I have gotten the logon.scr file but I don't want to use that screensaver at the logon screen...

 

[Radical924]

Bump... I still need help with this problem please...

 

[A Guy]

In Windows 7 Direct3D is not accessible until after a user is logged in for security reasons. Many screen savers, including those provided with Windows, require Direct X and they may not work as Log on screen saver

   Note

This will only work using the blank black C:\Windows\System32\scrnsave.scr screen saver as the value for SCRNSAVE.EXE. Using any other screen saver will result in this error below when it tries to run from the log on screen.

http://www.sevenforums.com/tutorials/55389-log-screen-saver-enable-disable.html

It apparently will work if you use the LOGON.SCR file from an earlier operating system, like Vista.

The instructions seem to infer you can use a custom .scr if you change the path to the correct string. Did you place your custom screensaver to C:\Windows\System32 ? I think it will only work with a screen saver specifically designed to not need Direct 3D. A Guy

 

[Radical924]

There is no way to enable the Direct 3D support at the log-on screen for screensavers at all? Are you sure because I don't understand why a lot of sites would suggest being able to use other screensavers (Including windows screensavers like Mystify etc...) if they don't actually work... Anybody here know any way of enabling Direct 3D at the log-on screen???

 

[Radical924]

bump......

 

[Stephanie]

Hi Radical924

Your GPU as your system specs is a NVIDIA GeForce 6150SE nForce 430, do you have the latest drivers ?

 

[Radical924]

Hi Radical924

Your GPU as your system specs is a NVIDIA GeForce 6150SE nForce 430, do you have the latest drivers ?

Yeah I do... That is why it confuses me...... Maybe there is some registry key that turns it off on the logon screen that I can change?

 

[Anak]

There has been no mention of a registry backup being made, it is cheap insurance, but that is entirely up to you.

It is imperative that you have the latest DirectX. Do you?

Also I have gotten the logon.scr file but I don't want to use that screensaver st the logon screen...

Keep this in mind. This file may need to be placed in the same exact Windows 7 folder location that you copied from your Vista disk.

What did you mean by the st after screensaver???


What are you using for the registry value; SCRNSAVE.EXE , can you post a screenshot of that whole hive before you try my suggestions?

And please, read through both my suggestions before proceeding, if you have any questions before proceeding, please ask but we will take each suggestion one at a time.

~~~ Suggestion #1 ~~~
​

Now, according to your tutorial the registry values should be, and make sure:

• The spelling is correct especially if you typed them in yourself.
• There are no quotation marks or equal signs, and no spaces.
• The type of key should be automatic. REG_SZ
• It should look like this, and note the double back slashes.

 Name                Type    Data
ScreenSaveActive             1
ScreensaveTimeOut            60 [COLOR=Blue][I](or your preference, see tip)[/I][/COLOR]
SCRNSAVE.EXE                 C:\\Windows\\Sytem32\\[COLOR=Blue](your custom screensaver file location here .scr)[/COLOR]             
[U][B]Or see below: [/B][/U]
SCRNSAVE.EXE                 C:\\Windows\\System32\\Matrix\\[COLOR=Blue](your custom screensaver file location here .scr)[/COLOR]

If the double back slashes don't work try a single \ .

Your tutorial suggests the SCRNSAVE.EXE C:\\Windows\\System32\\ line should be: C:\Windows\System32\Matrix\ whatever-the-name-is .scr or you can try the variation as shown above in the Code box.

If the double, single backslashes or adding Matrix did not work, try adding the logon.scr file you extracted, to the corresponding Folder location in C:\Windows\ check after each variation before you move onto the next.

There can be six variations to this with trying with or without the logon.scr file. If C:\\Windows\\Sytem32\\(your custom screensaver file location here .scr) doesn't work, but, it does after adding the logon.scr file you're home free.

~~~ Suggestion #2 ~~~
​

Another way to try is from this thread: How to get a screensaver at the Windows 7 login screen? - Super User Here it suggests the values should be:

 Name                Type    Data
ScreenSaveActive             1 
ScreenSaveIsSecure           0 
ScreenSaveTimeOut            60 [COLOR=Blue][I](or your preference, see tip)[/I][/COLOR]
SCRNSAVE.EXE                 C:\WINDOWS\SYSTEM32\LOGON.SCR

Note the added Key Name, ScreenSaveIsSecure 0 ; This tutorial suggests this value can either be 0 or 1.

The 0 means the ScreenSaveIsNotSecure, 1 does. If you have to log-in I would think to try a value of 1 first.
And it can also be either ScreenSaveIsSecure 0 or ScreenSaverIsSecure 0, note the added r in the second example.


You can either leave the SCRNSAVE.EXE C:\WINDOWS\SYSTEM32\LOGON.SCR as is or you can try SCRNSAVE.EXE C:\WINDOWS\SYSTEM32\(your custom screensaver file location here .scr) in either variation the logon.scr file needs to be in its proper location.

   Note

• In both tutorials the Key Name SCRNSAVE.EXE is the only Key Name that is capitalized.
• In your tutorial the logon.scr file is placed in the system32 Folder.
• In suggestion #2 it is also placed there in the instructions, but the screenshot shows it placed in the SystemWOW64 Folder. This may be because of the difference in 32 and 64bit Operating Systems. If it doesn't work in System32, and since you have a 64bit system, try the SystemWOW64 Folder.
• Placing logon.scr in the SystemWOW64 Folder may also hold true for suggestion #1 no mater what Folder you copied it from the Vista disk because you have a 64bit system.

   Tip

This is how the ScreenSaveTimeout is configured:

• 60 = 60seconds
• 30 = 30seconds
• 15 = 15seconds

and so on.

If you want to go longer, multiply the number of minutes by 60:

• 5minutes x 60 = 300
• 10minutes x 60 = 600
• 15minutes x 60 = 900

and so on.

 

[Radical924]

There has been no mention of a registry backup being made, it is cheap insurance, but that is entirely up to you.

Alrighty then I just made a System Restore Point.

It is imperative that you have the latest DirectX. Do you?

Yeah I just tried installing "Windows6.1-KB2670838-x64" and it says the update is already installed.

Also I have gotten the logon.scr file but I don't want to use that screensaver st the logon screen...

Keep this in mind. This file may need to be placed in the same exact Windows 7 folder location that you copied from your Vista disk.

What did you mean by the st after screensaver???

I meant to say "at" not "st"... sorry for the spelling mistake. Also I know that the screensaver might have to be placed in the same folder as on Vista and that is what I am doing. I just don't want the Logon.scr screensaver... I want a custom screensaver (Once we can get the preset screensavers to work on the logon screen).

What are you using for the registry value; SCRNSAVE.EXE , can you post a screenshot of that whole hive before you try my suggestions?

Okay here is the screenshot:

I'll wait for a response before I try to follow any of your suggestions. Thank you for the response!

 

[Anak]

Your welcome,

A system restore point could suffice, but it is not the same as a registry backup.

I need to know the designation of the operating system (OS) you have. You do not show service pack1 in your system specs, is your OS SP1 or not??
Please see this tutorial and post a screenshot: System Information

Your mention of Windows6.1-KB2670838-x64.msu could be a problem with Updates, how do you have them set, have you tried to force a check for Updates?
After you run the SFC scan (see end of post) attach the .CBS Log along with the two below. How to find the .CBS log is in Option Three of the SFC link below.


Then go here: DirectX Diagnostic Tool you will see a progress bar to the lower left, when it is done click on save all information (to your desktop) then run the 64bit side of DirectX (second button from the left) and save that, then post both files in your next reply.

No problem with the spelling, I had a feeling that was what you meant.
The logon.scr file is not a screensaver per se, but it is what tells the OS to continue to search for the next line in your registry, such as;

SCRNSAVE.EXE                 C:\\Windows\\Sytem32\\(your custom screensaver file location here .scr)

Your hive looks okay.
As long as you have the registry backup I see no reason why you couldn't experiment by adding the double \\ as shown in the above code box. Then see if the ribbon.scr plays, if it doesn't and you have the logon.scr in place

I know that the screensaver might have to be placed in the same folder as on Vista and that is what I am doing.

just rename it to logon.scr_old and see if it plays then. If it does you can either leave it or remove it. Then try replacing ribbon.scr with the file location of your custom screensaver but remember to change the file extension to .scr, by the way what is the file extension of your custom saver?

When was the last time you restarted your machine, ran a chkdsk, SFC scan, antimalware scans, disk cleanup?
It's not written in stone, but it would be good to restart after making registry changes.


I had a long day after I posted to you earlier and its late now, I won't be able to check back till late tomorrow morning, maybe afternoon.

 

[Radical924]

Your welcome,

A system restore point could suffice, but it is not the same as a registry backup.

I need to know the designation of the operating system (OS) you have. You do not show service pack1 in your system specs, is your OS SP1 or not??
Please see this tutorial and post a screenshot: System Information

Your mention of Windows6.1-KB2670838-x64.msu could be a problem with Updates, how do you have them set, have you tried to force a check for Updates?
After you run the SFC scan (see end of post) attach the .CBS Log along with the two below. How to find the .CBS log is in Option Three of the SFC link below.


Then go here: DirectX Diagnostic Tool you will see a progress bar to the lower left, when it is done click on save all information (to your desktop) then run the 64bit side of DirectX (second button from the left) and save that, then post both files in your next reply.

No problem with the spelling, I had a feeling that was what you meant.
The logon.scr file is not a screensaver per se, but it is what tells the OS to continue to search for the next line in your registry, such as;

SCRNSAVE.EXE                 C:\\Windows\\Sytem32\\(your custom screensaver file location here .scr)

Your hive looks okay.
As long as you have the registry backup I see no reason why you couldn't experiment by adding the double \\ as shown in the above code box. Then see if the ribbon.scr plays, if it doesn't and you have the logon.scr in place

I know that the screensaver might have to be placed in the same folder as on Vista and that is what I am doing.

just rename it to logon.scr_old and see if it plays then. If it does you can either leave it or remove it. Then try replacing ribbon.scr with the file location of your custom screensaver but remember to change the file extension to .scr, by the way what is the file extension of your custom saver?

When was the last time you restarted your machine, ran a chkdsk, SFC scan, antimalware scans, disk cleanup?
It's not written in stone, but it would be good to restart after making registry changes.


I had a long day after I posted to you earlier and its late now, I won't be able to check back till late tomorrow morning, maybe afternoon.

1. Okay I do have Service Pack 1 so I changed that in my System Specs (I could swear it said that before in more detail).

2. The reason I mentioned Windows6.1-KB2670838-x64.msu was to see if I had the latest Direct X - which I do.

3. I opened DxDiag and it came up with a message talking about Direct3D... So I clicked no and it did whatever it was supposed to do without crashing... Here are the two logs: 32 BIT LOG ; 64 BIT LOG

4. I managed to get LOGON.SCR to work! Just not any other screensavers (Ribbons.scr) or I get the Direct 3D error... Still progress!!! I didn't use two backslashes, I set the screensaversecure value to 1 (Note the R at the end of screensaveR), I also kept LOGON.SCR in system32 not SysWow64.

5. I scan my pc and have it on automated disk defrags, scans, cleanups etc... So no worries in that department.

Anyways thank you for the response! I am glad we made some progress (I am just not sure what made LOGON.SCR work exactly)... So all that is left is the Direct 3D error so I can use a custom screensaver... If there is no way possible I am happy with LOGON.SCR.

Regards, Radical924

 

[Anak]

1. Okay I do have Service Pack 1 so I changed that in my System Specs (I could swear it said that before in more detail).

2. The reason I mentioned Windows6.1-KB2670838-x64.msu was to see if I had the latest Direct X - which I do.

3. I opened DxDiag and it came up with a message talking about Direct3D... So I clicked no and it did whatever it was supposed to do without crashing... Here are the two logs: 32 BIT LOG ; 64 BIT LOG

4. I managed to get LOGON.SCR to work! Just not any other screensavers (Ribbons.scr) or I get the Direct 3D error... Still progress!!! I didn't use two backslashes, I set the screensaversecure value to 1 (Note the R at the end of screensaveR), I also kept LOGON.SCR in system32 not SysWow64.

5. I scan my pc and have it on automated disk defrags, scans, cleanups etc... So no worries in that department.

Anyways thank you for the response! I am glad we made some progress (I am just not sure what made LOGON.SCR work exactly)... So all that is left is the Direct 3D error so I can use a custom screensaver... If there is no way possible I am happy with LOGON.SCR.

Regards, Radical924

Had some time before my day started so I wanted to squeeze this in.


1.) Wait till you get older, I'm always swearing in great detail.

2.) Good.

3.) Do you remember what the message said, can you recreate it?

3a.) Thank you for logs, I have them, but it won't be till later that I can comment on them after looking them over.

4.) That is good news! But, only with ribbons so far, eh?

4a.) Okay on the double \\ . These registry entries have to be exact. Note the spelling and capitalization; that screensaversecure you mention should be ScreenSaverIsSecure, I hope it is and you are abbreviating, otherwise your OS won't know where to look, if it isn't please change it and test.

4b.) You could try renaming logon.scr to old and copying it over to SysWOW64 to test.

5.) Good.

5a.) Your welcome! Progress is always a good thing. Maybe later I can try to explain logon.scr.

5b.) Did you try changing the file extension to your custom screensaver.scr?


Ketch Ya Later, Anak

 

[Radical924]

Had some time before my day started so I wanted to squeeze this in.

1.) Wait till you get older, I'm always swearing in great detail.

2.) Good.

3.) Do you remember what the message said, can you recreate it?

3a.) Thank you for logs, I have them, but it won't be till later that I can comment on them after looking them over.

4.) That is good news! But, only with ribbons so far, eh?

4a.) Okay on the double \\ . These registry entries have to be exact. Note the spelling and capitalization; that screensaversecure you mention should be ScreenSaverIsSecure, I hope it is and you are abbreviating, otherwise your OS won't know where to look, if it isn't please change it and test.

4b.) You could try renaming logon.scr to old and copying it over to SysWOW64 to test.

5.) Good.

5a.) Your welcome! Progress is always a good thing. Maybe later I can try to explain logon.scr.

5b.) Did you try changing the file extension to your custom screensaver.scr?


Ketch Ya Later, Anak

3) Okay here is the message: "DxDiag has detected that there might have been a problem accessing Direct3D the last time this program was used. Would you like to bypass Direct3D this time?" I don't know how to recreate this message... BTW I hit "No" not "Yes".

4) What I meant was I couldn't get Ribbons.scr to work or any others... Kinda bad on my part with the wording...

4a) Yeah I was just abbreviating... what I put down was ScreenSaverIsSecure. For the value I put 1.

4b) Okay I tried Logon.scr in the SysWow64 folder and it works as well BUT Ribbons.scr does not work in the SysWow64 folder... I get the Missing Direct 3D error...

5) Naw I didn't try changing the extension of my custom screensaver because I haven't tried it yet... I want to be able to get the default windows screensavers with Direct 3D to work at logon first before I try any custom ones. Also my custom screensaver has its own installer and I checked and inside where it installs is the screensaver file. It ends in .scr.

 

[Anak]

Been a long...day,


3.) There are a couple of steps I'd like you to do, this is tied in with your missing Direct 3D error in 4b.

• Reboot your machine and enter Advanced Boot Options go to Here's How Step #3 then to "Last known good configuration" touch enter or return to finish the reboot. Open DxDiag and see if you get the error message again.
• Even if you don't I would really like you to run CHKDSK, on the HDD you have your OS on, I warn you it could take several hours or more to complete so be patient. Then SFC /scannow on your OS HDD twice with reboots in between even if the first run says there were no integrity violations. The two SFC scans shouldn't take longer than a half/hour.

4. and 4a.) Okay, no harm just clarifying.

4b.) I went over your Dx logs and they seem to be incomplete that may be why your getting the error, I haven't been able to figure it out yet. My Dx log shows two extra sound tabs to your one.

------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
        Sound Tab 2: No problems found.
        Sound Tab 3: No problems found.
          Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D:    0/4 (retail)
DirectDraw:  0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay:  0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow:  0/6 (retail)

[U][B]Yours:[/B][/U]
------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
         Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D:    0/4 (retail)
DirectDraw:  0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay:  0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow:  0/6 (retail)

5.) We'll let that go for now.

6.) After you run that SFC scan see the bottom of the tutorial and please send me the .CBS log, it can help to pinpoint any corrupt files.


That's it for me, I won't be back in-forum till tomorrow, talk with you later.

 

[Radical924]

You know what I am fairly sure based on the threads I have read the Direct 3D is not supported at the logon screen and their is no way to enable it... You have done more than enough to assist me so far and I am grateful for that. I am glad we managed to get logon.scr to work so I am just going to stick with that.

I would further troubleshoot and follow the steps you provided but they are a bit much and I know that they probably won't help unfortunately cause I was just reading other threads and these things were also suggested and didn't resolve the issue... However, I would still like screensavers that don't use Direct3D, so if you know where I can find screensavers that don't need Direct 3D support that would work great!?!?!

I hope I didn't annoy in any way but you know you already helped me out as much as I really need... Now I have a screensaver and I am happy with that. Thank you! The only thing that confuses me is why it was telling me to use custom screensavers and it wasn't specifying that they can't be direct3d...

In any case you were a real help... thank you so much!

 

[Anak]

You may be right, don't know if you've seen this: No screen saver at Windows 7 welcome/log in screen. - Microsoft Community If I do run across a way to enable it I'll remember you.
Okay, and thank you for your kind words.

Keep the CHKDSK and SFC scans in mind, if you continue to have errors that are connected with the operating system they should help.
You know I just might have something up your alley, take a look at this: LogonStudio - Apply and Package New Logon Screens

Be careful if you decide to use it. I didn't go further, but you'll have to click on the download button in two locations, then it will ask you for your email address, they do this because they want you to create an account with them.

You can go to a site like: Download LogonStudio 1.7.0 | Softpedia or Download LogonStudio - MajorGeeks where you won't see that behaviour. Watch when installing and clicking next, you wouldn't want any PuPs (Potentially unwanted Programs) would you?


Google search for videos about LogonStudio

If you do go with LogonStudio (LS) you may have to undo the changes to your registry in case LS won't work, I'd leave the registry as is until you find out if LS runs okay or not.


No worries mate! It was my pleasure to assist you.

The confusion may stem from the Vista logon.scr file you extracted and placed in the Windows 7 system32 Folder, where logon screensavers were allowed in Vista but not in 7.


Here is some info on logon.scr:
logon.scr Windows process - What is it?

Don't let this one scare you, from where you got it, its safe.
SystemLookup - logon.scr - Global Search