Vista - desktop background changing to black

Hi.
I have the following problem with my vista home premuim. whenever i
change my desktop background to any background, the background stays
there until i turn off my computer. the next time i turn it on, the
background is black again. any ideas? btw, i have dell inspirion 6400.

Hi Montyphyton,

Not sure, but check this link out to see if it applies to you:

http://support.microsoft.com/kb/934008

Hope it helps,
Shawn

Hi, Monty.

Where is your "wallpaper" stored? Is it on a network or thumb drive or
other location that might not be available when your computer starts? Maybe
all you need to do is move (or copy) that file onto a location that is
always available to Vista.

RC
--
R. C. White, CPA
San Marcos, TX
rc@grandecom.net
Microsoft Windows MVP
(Running Windows Live Mail desktop beta in Vista Ultimate x64)

<montyphyton@gmail.com> wrote in message
news:1180001070.997851.51230@w5g2000hsg.googlegroups.com...
> Hi.
> I have the following problem with my vista home premuim. whenever i
> change my desktop background to any background, the background stays
> there until i turn off my computer. the next time i turn it on, the
> background is black again. any ideas? btw, i have dell inspirion 6400.

R. C. White [MVP] je napisao/la:
> Hi, Monty.
>
> Where is your "wallpaper" stored? Is it on a network or thumb drive or
> other location that might not be available when your computer starts? Maybe
> all you need to do is move (or copy) that file onto a location that is
> always available to Vista.
>

all the wallpapers are on my local disk, im using normal backgrounds
that came with vista.

brink je napisao/la:
> Hi Montyphyton,
>
> Not sure, but check this link out to see if it applies to you:
>
> '_http://support.microsoft.com/kb/934008_'
> (http://support.microsoft.com/kb/934008)
>

i've tried to edit the group policy the see what are my settings but
got an error that windows can't open gpedit.msc file. i've looked in
system32 folder and really, there is no such file there. i do have
gpedit.dll file there. this gpedit.msc seems like a kind of file i
really should have, shouldn't i?

I don't think the Home versions (even Premium) of Vista have a policy editor.

This is an odd problem. Was Vista the original OS on this computer? If not,
was it installed as an upgrade?

"montyphyton@gmail.com" wrote:

>
> brink je napisao/la:
> > Hi Montyphyton,
> >
> > Not sure, but check this link out to see if it applies to you:
> >
> > '_http://support.microsoft.com/kb/934008_'
> > (http://support.microsoft.com/kb/934008)
> >
>
> i've tried to edit the group policy the see what are my settings but
> got an error that windows can't open gpedit.msc file. i've looked in
> system32 folder and really, there is no such file there. i do have
> gpedit.dll file there. this gpedit.msc seems like a kind of file i
> really should have, shouldn't i?
>
>

Sorry,

I'm at a loss on this one. My 64 Home premium didn't have the file either.

Shawn

jimmuh je napisao/la:
> I don't think the Home versions (even Premium) of Vista have a policy editor.
>
> This is an odd problem. Was Vista the original OS on this computer? If not,
> was it installed as an upgrade?
>
> "montyphyton@gmail.com" wrote:
>

i've checked it on the net and you're right - vista home editions dont
come with the option for editing group policies. as for my vista, it
came as the original OS on my laptop. i haven't tampered with it, this
stuff was happening from day one...

Have you communicated with the vendor of the computer? Sounds like something
is fishy with their original system image. Does everything else seem to be
functioning properly?

I really should get off my duff and do some investigating. I have become
complacent since the advent of Vista, relying solely upon active directory
and the policy editor to achieve whatever I want in the way of control of the
systems I support. But it would be useful to know the registry locations
affected by the policies. One can use a registry reference, or do it the fun
way -- using a tool like RegMon (Mark Russinovich, who now works for
Microsoft) to monitor for registry changes when the policy is applied. If I
get a chance to do play with this today I'll get back to you.

In the meantime, have you considered contacting the notebook vendor or
talking with Microsoft about the hotfix?

"montyphyton@gmail.com" wrote:

>
> jimmuh je napisao/la:
> > I don't think the Home versions (even Premium) of Vista have a policy editor.
> >
> > This is an odd problem. Was Vista the original OS on this computer? If not,
> > was it installed as an upgrade?
> >
> > "montyphyton@gmail.com" wrote:
> >
>
> i've checked it on the net and you're right - vista home editions dont
> come with the option for editing group policies. as for my vista, it
> came as the original OS on my laptop. i haven't tampered with it, this
> stuff was happening from day one...
>
>

jimmuh je napisao/la:
> Have you communicated with the vendor of the computer? Sounds like something
> is fishy with their original system image. Does everything else seem to be
> functioning properly?
>
> I really should get off my duff and do some investigating. I have become
> complacent since the advent of Vista, relying solely upon active directory
> and the policy editor to achieve whatever I want in the way of control of the
> systems I support. But it would be useful to know the registry locations
> affected by the policies. One can use a registry reference, or do it the fun
> way -- using a tool like RegMon (Mark Russinovich, who now works for
> Microsoft) to monitor for registry changes when the policy is applied. If I
> get a chance to do play with this today I'll get back to you.
>
> In the meantime, have you considered contacting the notebook vendor or
> talking with Microsoft about the hotfix?
>

not really because everything else works fine and this isn't some
really big problem. and also, i'm currently in france (bought the
laptop here too) and technical french isn't my strong side. can't
understand a word the lady from dell says on the phone needles to
say her english is worse than my french. anyway, for now i'll live
with it. one thing, though. i've disabled cyberlink power cinema in
startup (the monster ate more than 500 MB of memory). don't really
think that is causing the problem, but maybe it's important to point
that out.