1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

"Preparing to Move" Window

Discussion in 'Windows Vista' started by Graham Newey, Oct 11, 2009.

  1. Graham Newey

    Graham Newey Guest

    Over the last few days, immediately after boot up, a small window pops up on
    my desktop.

    It's title is "Preparing to Move".

    It APPEARS to do precisely nothing and disappears, not to be seen again
    until I next boot up!

    Anybody got an idea what this is all about? Only seems to have been
    appearing over, say, the last week.

    OS is Vista Home Premium-64 bit.

    Look forward with interest to any comments,

    Regards,

    --
    GPN
     
  2. Peter Foldes

    Peter Foldes Guest

    Event Viewer say's what ?

    --
    Peter

    Please Reply to Newsgroup for the benefit of others
    Requests for assistance by email can not and will not be acknowledged.

    "Graham Newey" <GrahamNewey@discussions.microsoft.com> wrote in message
    news:B85F7C79-97F1-4C3A-98D0-CC967DE15D75@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Over the last few days, immediately after boot up, a small window pops up on
    > my desktop.
    >
    > It's title is "Preparing to Move".
    >
    > It APPEARS to do precisely nothing and disappears, not to be seen again
    > until I next boot up!
    >
    > Anybody got an idea what this is all about? Only seems to have been
    > appearing over, say, the last week.
    >
    > OS is Vista Home Premium-64 bit.
    >
    > Look forward with interest to any comments,
    >
    > Regards,
    >
    > --
    > GPN <!--colorc--><!--/colorc-->
     
  3. Graham Newey

    Graham Newey Guest

    Dear Peter,

    Thanks for rapid response.

    As will become evident, I am a COMPLETE newbie as far as Vista is concerned.

    My immediate reaction to your post was---"What is this guy talking about?"!!

    Anyway, I've found "Event Viewer", (an achievement in itself), and to be
    brutally frank, I'm none the wiser.

    Obviously, I need to study the "EW "Help" file, but in the meantime if you
    could possibly give me a few pointers (in words of one syllable) about using
    this tool to deal with my little problem I would be extremely grateful.

    When I started the comp this time I waited for the window to appear so that
    I could provide a bit more info on its contents. It DIDN'T appear! Sods law I
    suppose!!

    BTW without wishing to appear totally thick I didn't really understand the
    instruction to "Reply to Newsgroup".

    Regards,

    --
    GPN


    "Peter Foldes" wrote:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Event Viewer say's what ?
    >
    > --
    > Peter
    >
    > Please Reply to Newsgroup for the benefit of others
    > Requests for assistance by email can not and will not be acknowledged.
    >
    > "Graham Newey" <GrahamNewey@discussions.microsoft.com> wrote in message
    > news:B85F7C79-97F1-4C3A-98D0-CC967DE15D75@microsoft.com...<!--coloro:green--><span style="color:green <!--/coloro-->
    > > Over the last few days, immediately after boot up, a small window pops up on
    > > my desktop.
    > >
    > > It's title is "Preparing to Move".
    > >
    > > It APPEARS to do precisely nothing and disappears, not to be seen again
    > > until I next boot up!
    > >
    > > Anybody got an idea what this is all about? Only seems to have been
    > > appearing over, say, the last week.
    > >
    > > OS is Vista Home Premium-64 bit.
    > >
    > > Look forward with interest to any comments,
    > >
    > > Regards,
    > >
    > > --
    > > GPN <!--colorc--><!--/colorc-->
    >
    > <!--colorc--><!--/colorc-->
     
  4. Malke

    Malke Guest

    Graham Newey wrote:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > My immediate reaction to your post was---"What is this guy talking
    > about?"!!
    >
    > Anyway, I've found "Event Viewer", (an achievement in itself), and to be
    > brutally frank, I'm none the wiser.
    >
    > Obviously, I need to study the "EW "Help" file, but in the meantime if you
    > could possibly give me a few pointers (in words of one syllable) about
    > using this tool to deal with my little problem I would be extremely
    > grateful.
    >
    > When I started the comp this time I waited for the window to appear so
    > that I could provide a bit more info on its contents. It DIDN'T appear!
    > Sods law I suppose!!
    >
    > BTW without wishing to appear totally thick I didn't really understand the
    > instruction to "Reply to Newsgroup".<!--colorc--><!--/colorc-->

    Event Viewer will often give a clue to what has been happening with the
    system. You highlight Application or System in the left pane and entries
    will appear in the right pane. If there are red or yellow warnings, you
    double-click on one to see what it is. While it might not be clear to you,
    the error can then be Googled or posted back here for more help.

    Since the problem seems to have disappeared, you can stop worrying about it.
    If it comes back or for future problems of a like nature, here is the normal
    troubleshooting path:

    The First Question Of Troubleshooting: If the problem is new, what changed
    between the time things worked and the time they didn't?

    The Second Question of Windows Troubleshooting: what is the malware/virus
    status of the machine? If you think it is clean, what programs (and
    versions) did you use to determine this?

    Be sure the computer is clean:


    If you can't immediately answer The First Question and solve the problem
    that way, then go through the steps at the link to answer The Second
    Question. For a preliminary answer you might want to skip running Multi-AV
    if you have a good antivirus installed already, but don't skip the
    maintenance preparation and scanning with Malwarebytes' Anti-Malware (MBAM).

    If the computer is completely virus/malware-free and running MBAM didn't
    solve the issue, do clean-boot troubleshooting to find out what is running at
    Startup.

    How to troubleshoot a problem by performing a clean boot in Windows Vista -


    The free Autoruns program is very useful for managing your Startup -


    The "Reply to Newsgroup" is part of Mr. Foldes' signature and not part of
    his answer to you. It means in effect, "don't send me a personal email -
    reply to the newsgroup instead".

    Malke
    --
    MS-MVP
    Elephant Boy Computers - Don't Panic!
     
  5. Graham Newey

    Graham Newey Guest

    Dear Malke,

    Very much obliged by your detailed response.

    I have printed it, will attempt to digest it, and after a 2 hour lie down in
    a darkened room, will see what progress I make!

    Will advise further,

    Regards,


    --
    GPN


    "Malke" wrote:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Graham Newey wrote:
    > <!--coloro:green--><span style="color:green <!--/coloro-->
    > > My immediate reaction to your post was---"What is this guy talking
    > > about?"!!
    > >
    > > Anyway, I've found "Event Viewer", (an achievement in itself), and to be
    > > brutally frank, I'm none the wiser.
    > >
    > > Obviously, I need to study the "EW "Help" file, but in the meantime if you
    > > could possibly give me a few pointers (in words of one syllable) about
    > > using this tool to deal with my little problem I would be extremely
    > > grateful.
    > >
    > > When I started the comp this time I waited for the window to appear so
    > > that I could provide a bit more info on its contents. It DIDN'T appear!
    > > Sods law I suppose!!
    > >
    > > BTW without wishing to appear totally thick I didn't really understand the
    > > instruction to "Reply to Newsgroup".<!--colorc--><!--/colorc-->
    >
    > Event Viewer will often give a clue to what has been happening with the
    > system. You highlight Application or System in the left pane and entries
    > will appear in the right pane. If there are red or yellow warnings, you
    > double-click on one to see what it is. While it might not be clear to you,
    > the error can then be Googled or posted back here for more help.
    >
    > Since the problem seems to have disappeared, you can stop worrying about it.
    > If it comes back or for future problems of a like nature, here is the normal
    > troubleshooting path:
    >
    > The First Question Of Troubleshooting: If the problem is new, what changed
    > between the time things worked and the time they didn't?
    >
    > The Second Question of Windows Troubleshooting: what is the malware/virus
    > status of the machine? If you think it is clean, what programs (and
    > versions) did you use to determine this?
    >
    > Be sure the computer is clean:
    >
    >
    > If you can't immediately answer The First Question and solve the problem
    > that way, then go through the steps at the link to answer The Second
    > Question. For a preliminary answer you might want to skip running Multi-AV
    > if you have a good antivirus installed already, but don't skip the
    > maintenance preparation and scanning with Malwarebytes' Anti-Malware (MBAM).
    >
    > If the computer is completely virus/malware-free and running MBAM didn't
    > solve the issue, do clean-boot troubleshooting to find out what is running at
    > Startup.
    >
    > How to troubleshoot a problem by performing a clean boot in Windows Vista -
    >

    >
    > The free Autoruns program is very useful for managing your Startup -
    >

    >
    > The "Reply to Newsgroup" is part of Mr. Foldes' signature and not part of
    > his answer to you. It means in effect, "don't send me a personal email -
    > reply to the newsgroup instead".
    >
    > Malke
    > --
    > MS-MVP
    > Elephant Boy Computers - Don't Panic!
    >

    >
    > <!--colorc--><!--/colorc-->
     
  6. Graham Newey

    Graham Newey Guest

    --
    GPN


    "Malke" wrote:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Graham Newey wrote:
    > <!--coloro:green--><span style="color:green <!--/coloro-->
    > > My immediate reaction to your post was---"What is this guy talking
    > > about?"!!
    > >
    > > Anyway, I've found "Event Viewer", (an achievement in itself), and to be
    > > brutally frank, I'm none the wiser.
    > >
    > > Obviously, I need to study the "EW "Help" file, but in the meantime if you
    > > could possibly give me a few pointers (in words of one syllable) about
    > > using this tool to deal with my little problem I would be extremely
    > > grateful.
    > >
    > > When I started the comp this time I waited for the window to appear so
    > > that I could provide a bit more info on its contents. It DIDN'T appear!
    > > Sods law I suppose!!
    > >
    > > BTW without wishing to appear totally thick I didn't really understand the
    > > instruction to "Reply to Newsgroup".<!--colorc--><!--/colorc-->
    >
    > Event Viewer will often give a clue to what has been happening with the
    > system. You highlight Application or System in the left pane and entries
    > will appear in the right pane. If there are red or yellow warnings, you
    > double-click on one to see what it is. While it might not be clear to you,
    > the error can then be Googled or posted back here for more help.
    >
    > Since the problem seems to have disappeared, you can stop worrying about it.
    > If it comes back or for future problems of a like nature, here is the normal
    > troubleshooting path:
    >
    > The First Question Of Troubleshooting: If the problem is new, what changed
    > between the time things worked and the time they didn't?
    >
    > The Second Question of Windows Troubleshooting: what is the malware/virus
    > status of the machine? If you think it is clean, what programs (and
    > versions) did you use to determine this?
    >
    > Be sure the computer is clean:
    >
    >
    > If you can't immediately answer The First Question and solve the problem
    > that way, then go through the steps at the link to answer The Second
    > Question. For a preliminary answer you might want to skip running Multi-AV
    > if you have a good antivirus installed already, but don't skip the
    > maintenance preparation and scanning with Malwarebytes' Anti-Malware (MBAM).
    >
    > If the computer is completely virus/malware-free and running MBAM didn't
    > solve the issue, do clean-boot troubleshooting to find out what is running at
    > Startup.
    >
    > How to troubleshoot a problem by performing a clean boot in Windows Vista -
    >

    >
    > The free Autoruns program is very useful for managing your Startup -
    >

    >
    > The "Reply to Newsgroup" is part of Mr. Foldes' signature and not part of
    > his answer to you. It means in effect, "don't send me a personal email -
    > reply to the newsgroup instead".
    >
    > Malke
    > --
    > MS-MVP
    > Elephant Boy Computers - Don't Panic!
    >

    >
    > <!--colorc--><!--/colorc-->
     
  7. On Sun, 11 Oct 2009 09:28:02 -0700, Graham Newey wrote:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Over the last few days, immediately after boot up, a small window pops up on
    > my desktop.
    >
    > It's title is "Preparing to Move".
    >
    > It APPEARS to do precisely nothing and disappears, not to be seen again
    > until I next boot up!
    >
    > Anybody got an idea what this is all about? Only seems to have been
    > appearing over, say, the last week.
    >
    > OS is Vista Home Premium-64 bit.
    >
    > Look forward with interest to any comments,
    >
    > Regards,<!--colorc--><!--/colorc-->

    To add to the other replies, here is how I interpret your symptoms:

    Some program is (or was, I guess) running during the start-up of your
    computer that was moving a file or set of files from one place to another.
    The message you saw was put up by the system as part of doing that process.

    It might relate to an incomplete installation of some software, and it
    might have gone away because the installation finally completed
    successfully.

    I can't be totally sure that what I said is exactly correct, but it fits
    well with my experience.

    --
    Gene E. Bloch letters0x40blochg0x2Ecom
     

Share This Page