Windows xp registry background settings


















If you are not familiar with the Windows registry you should get a qualified computer technician to perform this restore for you as changing the registry can cause your computer to not boot up. How to get to your Windows XP registry:. Note: To open folders in the Windows Registry you have to press on the plus sign beside the folder. To close the folder simply press the minus sign. Try changing your wallpaper now. Also see How to bring back the Desktop tab when it is missing from the display properties.

Viewed 2k times. Claudiu Claudiu k gold badges silver badges bronze badges. Why do you want to change the colors by modifying the registry instead of using the documented API for changing the colors SetSysColors? Larry: cause i didnt know about the latter — Claudiu. Add a comment. Active Oldest Votes. Blorgbeard Blorgbeard And SystemParametersInfo for the wallpaper. Yes - although the way I read the question, he's only looking to change the color.

SetSysColors win32con. BTW, changing the backgroupnd by editing the registry using RegEdit isn't "programatically". Your email address will not be published. Learn about the latest security threats, system optimization tricks, and the hottest new technologies in the industry. Over 1,, fellow IT Pros are already on-board, don't be left out!

We handle this via scripting to set the wallpaper after the shell has started and send the relevant windows message to redraw the desktop. This does mean people see the original MS wallpaper briefly on first login, but it fixes itself pretty quickly. I did just see another reference regarding replacing the existing xxxImg0. So I'm now thinking that is not a functional way to even bother trying if Microsoft is just going to come along and wipe those out in the next build.

Something so basic and simple should not be this complicated to do. We just want to give our users an initial desktop wallpaper when they log in and allow them to change it if they wish. It works just fine using CopyProfile, but Microsoft has managed to screw up CopyProfile in Build and now I'm resorting to 'stupid pet tricks' to find a way to do what we've been doing the past 2 years using CopyProfile.

Can you share the command you use to "refresh the desktop"? Does it work if users are not administrators? I'm wondering if I can perhaps do a 'first time run' of a batch file to set the registry value for the wallpaper when the user logs in, and then execute this command after doing that.

It's not a command as such, it's a Windows API call. More info here:. In our case, we're already running an in-house program that generates the wallpaper at the relevant resolution, so it's fairly trivial for it to also call that function. There are probably freeware utils that will just call this function if needed. It doesn't require any particular privileges to run - it's not doing anything that needs admin rights. Another option would be to enforce a wallpaper with group policy, but presumably you just want to set an initial default but still allow the user to change it if they prefer?

Correct, we want to give the users a Desktop Wallpaper as their initial default, but then allow them to change it if they wish.

Hi JS The article that Kate Li referenced is a similar process with taking ownership, resetting file permissions, and copying various files to replace existing files. However, I saw someone reference in the comments of that article that when they applied a new build, i. I'm curious if this is something that you have encountered, or if after applying a new build your custom 'default' image files remained in tact? I also saw a few comments that this did not work on Surface Pro 3 tablets, which we have several Surface Pro tablets in our environment.

Make sure the put the desktop paper on a network folder all of your users have the permission to access. That would apply after the shell has started and although it would change the key, explorer would not redraw the desktop with the new wallpaper as a result until the next logon.

It also assumes you're using the same wallpaper on all devices, with no consideration of different resolutions, aspect ratios etc. I am looking at doing something similar in logic. I've created a batch file with numerous "reg" commands to add registry key settings into the HKCU, one of which is the WallPaper, and also has a command in it to hopefully redraw the desktop screen.

I plan to put a shortcut. When a new user logs in, they should inherit this ". The last command in this batch file then in turns deletes the.

So in theory, a new user will log in, run the shortcut that executes the batch file. The batch file will add a bunch of settings and configuration to the users' profile, redraw the desktop to get the initial desktop wallpaper, and then delete the shortcut so it doesn't run again for that user profile. We are an active directory domain environment, but prefer to accomplish things like this inside the clone image itself, since we do have some computers that are used as stand alone and not on the domain.

There are a few minor things that don't seem to come through with using this approach of setting various registry keys versus using CopyProfile. Like Windows Explorer doesn't keep the look and feel and the ribbon bar doesn't seem to be expanded like we prefer. And obviously the wallpaper doesn't come though nearly as easily!

Aside from the Wallpaper setting, I have run into an odd problem though in initial testing with this new approach. After a user logs in and gets their profile generated, when we later delete that user profile from the computer, reboot, and log back in as that user, you'd think since it is essentially a "new" user logging in again it would work the same.

But it doesn't. After logging in this time, that user has all of the Universal Windows Programs missing from the Start Menu. This is a rather large problem as our techs often delete a user profile when troubleshooting problems for our users.

So even if the Wallpaper setting comes through, having a broken Start Menu like this is not desirable. Not sure what the heck is happening to cause this though, or what we can even do about it. Honestly, the best solution for us would be for Microsoft to fix CopyProfile in build , or the next build, as that has worked just fine for us up until now with setting the Wallpaper, custom Start Menu, and other settings.

Perhaps they will fix it in the next build, and if so, we will just skip build But if not, the work I'm doing now will hopefully provide an alternate way to provide a similar user experience in our clone image.

Though the Start Menu problem with deleting the users' profile is a rather troubling problem. I think that's a known issue - there are a number of other threads on technet about the profile deletion process not being entirely clean.



0コメント

  • 1000 / 1000