Windows 10: Can't Change Custom Color

I used command prompt this time and it ran without any problem.





However after the command was run.
The Personalization>Custom Color settings still display the same behaviour.

Ran Sfc too and it found nothing.





I also ran dism.





I still have the same behaviour, as shown in my posted video.

 

That doesn't surprise me- depends what the problem is. If you can try with another user, then if that also fails the same way, suggest an in-place upgrade repair install which keeps all programs and data and most settings.

There's an outside possibility of some 3rd party program interference e.g. a shell extension I suppose, easy to test. However you found the problem remained in Safe Mode.

 

I'm not aware of any program that I've installed, which might be adding shell extension modifiers.

Also when I try to create another account, by going to Settings>Accounts>Family & other people.
I then select this.




This opens.




I select, I don't have this person's sign-in information

This dialog appears once I've made this selection.




I've clicked Retry more then half a dozen time and I'm unable to create another account.

 

Ok, try an in-place upgrade repair install.
Repair Install Windows 10 with an In-place Upgrade Installation Upgrade Tutorials

As for shell extensions- you'd be surprised. Anything that adds context menu entries adds a shell extension.
I doubt that's your problem here though- but some time when this is fixed try running Shellexview or Shellmenuview (free) - purely for education. That's assuming you've installed a program.

 

I have a system image, from before this started happening.
Would you suggest I try restoring form this image?
* * *
This is what happen, when trying to create USB installation media using the Media Creation Tool.





I guess I could try again and see if it works, but this doesn't seem right to me.

 

I can't tell you what your system image restores. If you think it was created when you did not have these problems, try it by all means. I would guess you don't know if you were able to create a new user when that image was created.

I would suggest trying the in-place repair first, as if that works, your data and programs will be as they are now, and you could still try the system image.

 

As it stands now.
I'm formatting my USB flash drive, (long format) and then I'm going to try and create the installation media again.
Yes, I haven't tried creating additional accounts, until you made the suggestion in your previous posts. So I have no idea if I'll be able to create an account, once I run the system image restoration.

Let me see if I can create the USB media, for doing an in-place repair.

*fingers crossed*

 

Create Bootable USB Flash Drive to Install Windows 10 Installation Upgrade Tutorials
BUT: whist you can use that (but don't boot to it)

- for an in-place repair you boot normally, then run setup.exe from the Win 10 install medium.

You can rt click and Mount the iso, then run setup.exe

See tutorial in previous post:
4. To Do a Repair Install of Windows 10 with an ISO file

A) If you have not already, you will need to download a Windows 10 ISO file.

B) Mount the ISO file.

C) Run the setup.exe file to start Windows 10 Setup. (see screenshot below)

 

Okay, thanks for the tips. *Smile
I'm still waiting for the flash drive to finish formatting.
Once that's finished, I'm going to try again to create the bootable installation media.
I think I might place the flash drive in a different port this time.

 

Well, I did the in-place repair using the ISO file, because for some reason, I wasn't able to create a bootable USB flash drive.
Anyway, everything went well and it was up and running very quickly.
However,
this behaviour, as seen in my posted video is still present.*Confused

What the heck? *Sad

 

Hi, following the in-place repair install can you now create a new user successfully?

As you still have the problem, it's not basic Windows corruption- unless it's something an in-place repair doesn't repair e.g. some registry key.

It could be - user profile corruption - which an in-place repair won't repair.
It could be- some interaction with an installed program.

Therefore I return to the earlier ideas of
- creating a new user
- disabling shell extensions (perhaps not all are disabled in Safe Mode).

 

Fortunately, I was able to create another account.
This custom color change behaviour isn't present with the new user's account.

I also download shexview and had a look at it, but I really don't know what to look for.
What do you feel would be my best approach at this point?

 

Good- two points of progress- you've now been able to create an account, and now begun a diagnostic process, so the in-place repair seems to have achieved something, if perhaps incidental to the initial problem.

Best create a system restore point or back up your registry before doing this for extra security. (Shouldn't be necessary but safe practice)
If unsure on those, research them with a search engine.

Shellexview:
1. Make sure Hide All Microsoft Extensions and 32 bit Shell extentions are ticked as shown




2. click in the area shown in yellow above on empty space
3. press CTRL A to select all
4. Rt click an item, click Disable selected items.




Now try your bug.

If bug still present, reverse the above.

If bug not present, enable half and retry.
Continue disable/enable until you find the rogue extension.

A search engine can really help you: i searched for "using shellexview"
How To: Diagnose PC Issues using ShellExView | Daves Computer Tips
ShellExView Tutorial 2 - Using ShellExView | Top Windows Tutorials
How to Disable Shell Extensions with ShellExView: 13 Steps

- and lots more...

Note that Shellexview does not list ALL shell extensions, so you can try a similar process with Shellmenuview.

If that does not help- and it may not then...
Compare what is running between your two user accounts.(Screenshots can help here e.g. of task manager details etc)Otherwise you're left with a corrupt user profile, and need to start using a new one.

Note: in general, provided you encounter and notice a problem in time (i.e. not months after it actually occurred, which can happen, using System Restore routinely and regular disk imaging can give you recovery options. But if the problem has been there a long time, well that becomes more difficult.

 

This is what shexview looks like, with microsoft and 32bit shell extensions set to hide.
Can this be possible?

 

You should turn off "Show 32-bit Shell Extensions" option.