Classic Shell no longer in development, and now open source

Page 79 of 79 FirstFirst ... 2969777879

  1. Posts : 56,830
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #781

    This is a Dell driver. What does it have to do with Classic Shell, Open Shell, any Shell? Go to the directory indicated in the pic you posted and UNBLOCK the Setup.exe. It came from DELL. It's in the normal directory where DELL puts things.

    Classic Shell no longer in development, and now open source-2019-08-04_18h33_04.png
      My Computers


  2. Posts : 6,851
    22H2 64 Bit Pro
       #782

    Open an Elevated Command Prompt:

    Open Elevated Command Prompt in Windows 10

    Type:

    net user administrator /active:yes


    Then logout and choose Administrator on the login screen to login, it should be no passwords needed to login by default. (or the one you have previously configured)


    Login with the built-in admin account and install the driver from there.

    Use the Dell Drivers setup file path in your hard to read screenshot.


    Once installed, open Elevated Command Prompt and run the command below to turn off the built-in admin account:

    net user administrator /active:no

    Edit: Other option is to launch Autoruns and disable the entry.
    Last edited by Callender; 04 Aug 2019 at 19:26.
      My Computer


  3. Posts : 56,830
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #783

    Try post #781 first, if no luck, do #782.

    It's probably an unsigned driver.
      My Computers


  4. Posts : 26,452
    Windows 11 Pro 22631.3527
       #784

    f14tomcat said:
    Try post #781 first, if no luck, do #782.

    It's probably an unsigned driver.
    This is what happens when people do not make a new thread for their Problem. It should not just be added to an existing thread that has nothing to do with their issue.
      My Computer


  5. Posts : 308
    Win10
       #785

    f14tomcat said:
    Just a little confused. The red error message in your post and the pic of Classic Shell are mismatches. One has nothing to do with the other. The red error is a setup.exe for some driver, Classic Shell is not that driver. Never seen it associated with Classic Shell. Unless I'm totally misreading this post.

    Classic Shell no longer in development, and now open source
    f14tomcat said:
    This is a Dell driver. What does it have to do with Classic Shell, Open Shell, any Shell? Go to the directory indicated in the pic you posted and UNBLOCK the Setup.exe. It came from DELL. It's in the normal directory where DELL puts things.

    Classic Shell no longer in development, and now open source-2019-08-04_18h33_04.png
    Josey Wales said:
    This is what happens when people do not make a new thread for their Problem. It should not just be added to an existing thread that has nothing to do with their issue.
    NO, my problem is with classic shell. I said an error message SIMILAR to that one since I can't get a screenshot of the actual message because I can't get screen snipe to launch and it doesn't store when I hit the "PnSc" button.

    Switching to open shell seems to have worked, thanks for all the help and sorry for the confusion.
      My Computer


  6. Posts : 56,830
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #786

    Soapm said:
    NO, my problem is with classic shell. I said an error message SIMILAR to that one since I can't get a screenshot of the actual message because I can't get screen snipe to launch and it doesn't store when I hit the "PnSc" button.

    Switching to open shell seems to have worked, thanks for all the help and sorry for the confusion.
    Glad you got something to work. Yes, nuances of the meanings of words and phrases in relationship to others can get confusing, and lead to misinterpretations. Happy to see you're all fixed up now.
      My Computers


  7. Posts : 5,048
    Windows 10/11 Pro x64, Various Linux Builds, Networking, Storage, Cybersecurity Specialty.
       #787

    What?

    Classic Shell should work without issue on a Dell system (and *many* others!). It has nothing to do with it.
    Cleanly remove Classic Shell and all it's directories, including any hidden files and registry keys.

    Try reinstalling with admin privileges.

      My Computer


  8. Posts : 56,830
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #788

    Compumind said:
    What?

    Classic Shell should work without issue on a Dell system (and *many* others!). It has nothing to do with it.
    Cleanly remove Classic Shell and all it's directories, including any hidden files and registry keys.

    Try reinstalling with admin privileges.

    Who are you replying to? I think Josey already suggested to re-install it. But, OP is happy now, and up and running.
      My Computers


  9. Posts : 5,048
    Windows 10/11 Pro x64, Various Linux Builds, Networking, Storage, Cybersecurity Specialty.
       #789

    f14tomcat said:
    Who are you replying to? I think Josey already suggested to re-install it. But, OP is happy now, and up and running.
    Thought that the OP was referring to Open-Shell but wanted Classic Shell.

    Sorry for any confusion.
      My Computer


  10. Posts : 56,830
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #790

    Compumind said:
    Thought that the OP was referring to Open-Shell.but wanted Classic-Shell. No worries.
    Had some weird permission issues with CS, and installed OS over it, and all works now. Maybe he just got a bad CS installer, don't know. He's running OS now. I have CS running almost everywhere with no problems, OS on a couple of VMs, just because it's there.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 04:44.
Find Us




Windows 10 Forums