Recommended Posts

Today when i turned on my computer.. i noticed that my Vis wasnt on so i went to display properties and tried to put my vis on again, but then i got this error:

---------------------------

Error Loading Visual Styles

---------------------------

The visual styles could not be loaded because the file failed to load.

Details:

---------------------------

OK

---------------------------

And i get that no matter what i choose.. the only one i can have is the classic. windows xp luna and silver etc dont work either...

I dont remember uninstalling/installing anything so i dont think that could be it.. any ideas?

Link to comment
https://www.neowin.net/forum/topic/219992-cant-use-visual-styles/
Share on other sites

I tried what you just said with the net start themes and a dos prompt came up then disappeared fast, so i tried selecting a vis theme and got the error message again.

When i go Start >> Run >> cmd then type net start themes it says

  Quote
The requested service has already been started.

More help is available by typing NET HELPMSG 2182.

When i type NET HELPMSG 2182, it says
  Quote
The requested service has already been started.

EXPLANATION

You tried to start a service that is already running.

ACTION

To display a list of active services, type:

        NET START

Any help? :(

I had the same problems when patching my uxtheme.dll with the neowin patcher, downloaded a pre-patched from a site (someone knows the adress?), replaced with replacer - done.

Is the preview still looking like windows classic - even though you have loaded a new? Then do what I did.

OK, kinda late reply here but ived tried everything, replacing manually with replacer etc and nothing.

Here is clarification just in case:

OK, i go to display, then appeareance.. in the first drop down list i choose another vs, and a second after i choose it i get the error i show in first post, and the preview still is on the classic one.

Also, if i chose a different color scheme for the classic , it shows in preview, but when i press Apply (or OK) it seems to be working, but then i get the crashed app thingy with the error report for "Run DLL as an App" and then Display properties window closes and nothing is different..

i tried using SFC /scannow and it did find some stuff but didnt help..

  bcheck said:
I have had this exact problem for a while, and finally found a solution that fixed it for me:

http://www.mcse.ms/message1004436.html

That looked really promising, but when i tried it it didn't work! Thanks for trying, though!

In the new account, i also tried to change the style there and it didnt work..

  Quote
OK, kinda late reply here but ived tried everything, replacing manually with replacer etc and nothing.

I did, as I said... I guess I will try again, can't right now though. :pinch: Progress on this later.

In the meantime, all other ideas are welcome!

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Err more info required... Are you using the built-in VPN client? PowerShell > Batch. Either way, the script will most likely use rasdial.
    • The viewing figures in season 2 plummeted after 1 of the main characters died in season 2 episode 1. I think hbo is regretting listening to him so they got rid of him.
    • Google Workspace now lets you use custom AI Gems directly in Docs, Gmail, and more by Paul Hill Google Workspace users can now access Gems from the side panel of Google Docs, Slides, Sheets, Drive, and Gmail. Previously, Gems could only be accessed from the Gemini app directly. For anyone not familiar with Gems, they’re a more advanced feature in Gemini where you can make your own chatbots, powered by Gemini, with custom instructions. If you’re interested in learning more about them, check out my editorial from April, where I argue custom AI bots are the best thing about generative AI and how to create your own bots. The decision to make Gems available across Google Workspace has the potential to significantly speed up people’s workflows if they’ve started using Gems already. If you’ve never made a Gem, Google has several pre-made ones including a Brainstormer, Writing editor, Coding partner, and Learning guide. Google Workspace users can leverage Gems in an almost infinite number of ways. For example, imagine if you’re a teacher in whatever country and you have to make lesson plans for your class that must follow a certain structure, you can use natural language to program a gem to expect certain inputs from you (such as grade, subject, topic etc) and get an output that follows the required guidelines. If you’re a journalist, you could create a gem to quickly strip out the key bits of news from a press release or if you’re a student you can create a bot to break down complicated subjects into something easier to understand. The possibilities are nearly endless and now the Gems you make are even more accessible. Google mentioned that Gems can be accessed via the side panel of all supported Workspace applications and can be used across Workspace capabilities including @ mentioning, accessing files and folders, and more. If you need to create a Gem, you’ll still need to do that on the Gemini website. To get started with Gemini in Google Workspace, just click the “Ask Gemini” (spark button) in the top-right corner. Google said that the Gems feature rollout is an extended rollout which means it might take more than 15 days to get the feature. Admins out there do not need to do anything and there are no specific admin controls in the side panel for Gems or Gemini.
    • Microsoft changes hit Teams Android devices: Disable Entra ID policy to restore sign-in by Paul Hill As part of its Secure Future Initiative, Microsoft has deployed a new Entra ID Conditional Access policy targeting Device Code Flow authentication. Unfortunately, it has led some Microsoft Teams-certified Android devices (Teams Rooms on Android, Teams Phones, Teams Panels, and Teams Displays) to be logged out and signing back in can be a bit fiddly so guidance has been shared. Microsoft said that it shared previous guidance which explained how to exclude Android devices, but it seems some admins didn’t catch this as many devices were not excluded and have been signed out. It’s important to realize that this is not a bug, it’s a security feature. However, the move could have been better communicated. To sign the devices back in, you can do so manually. However, if the devices are remote you’ll need to follow these steps: By disabling the “Block device code flow” policy in step 1, it will change everything back to how it was before Microsoft decided to enable it to boost security. This will allow you to get those affected Android devices logged back in again. Also pay special attention to step 2 which says you might need to reboot your device three times. Once you have your Android devices logged in again, it’s probably a good idea to follow Microsoft’s previous guidance and add these to an exclusion list before re-enabling the “Block device code flow” policy. Microsoft recommends only allowing DCF where it’s absolutely necessary and then blocking it elsewhere. The best thing to do is to add your Teams Android device to the exclusion list - this will allow these devices to operate normally, while boosting overall security. If you’re an admin and have been impacted by this, be sure to take proactive measures to avoid disruptions in the future.
  • Recent Achievements

    • Reacting Well
      SteveJaye earned a badge
      Reacting Well
    • One Month Later
      MadMung0 earned a badge
      One Month Later
    • One Month Later
      Uranus_enjoyer earned a badge
      One Month Later
    • Week One Done
      Philsl earned a badge
      Week One Done
    • Week One Done
      Jaclidio hoy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      434
    2. 2
      ATLien_0
      158
    3. 3
      +FloatingFatMan
      146
    4. 4
      Nick H.
      65
    5. 5
      +thexfile
      62
  • Tell a friend

    Love Neowin? Tell a friend!