Vista please wait long time

Please advise. Approx how much time are you talking about? Steve R Jones ,. Log in or Sign up to hide this advert. Well, if Toshiba can't fix their very own, brand new laptop, maybe they should provide you with a new one?

Split ' ',[System. I am getting this issue on two machines using Remmina in a Linux VM Hi, I have the same problem, any solution? Then open Task Manager.

Navigate to users. Locate the user account which has hanged i. Right click on the user name and select reconnect. Type in the password. Get connected to the desired account. The issue for me was using the saved credentials to connect. I am on macOS and set the option to "Ask when required" for credentials.

Short term solution but hope this helps. To solve this: I use another remote PC and execute a remote restart command. Related Questions. Even am facing the same problem. The blue screen with a message "please wait" in start menu for ever, there is a cancel option but it doesn't work. I have updated the OS from windows 8 to 8. This is a new laptop which is not even a month old. What is the issue with the same?

Didn't find what you were looking for? Ask the community. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Search instead for. Did you mean:. Need Windows 11 help? Check documents and videos on compatibility, FAQs, upgrade information and available fixes. Windows 11 Support Center. Create an account on the HP Community to personalize your profile and ask a question. Your account also allows you to connect with HP support faster, access a personal dashboard to manage all of your devices in one place, view warranty information, case status and more.

It has been a while since anyone has replied. Simply ask a new question if you would like to start the discussion again. While we prepare for the move, we are unable to accept new postings. I have exactly the same issue as A.

Hohensee and wondered if there has been any progress on this. My client's laptop is a Lenovo Ti with Windows 7 Pro and is not a member of a domain, using only local profile.

So far, I've tried:. Always the same result and I can't pinpoint which update it is that breaks it. Any help appreciated. I was wondering if you were able to get anywhere with this issue. I too am in the same boat and have tried all the above with no luck. That same problem started with my new Dell laptop E , running Windows 7 Enterprise.

Through "msconfig", I disabled it both from the "Services" and "Startup" tabs - the system came up fine. I did not have to disable NLA or any other services. Even if first run repair commands in recovery console.

If that still causes the stall at start up, then change the service to Manual so that the OS can still fire up the service if it is required. Once the setting change is complete, the laptop should boot up and display the logon screen in essentially the same amount of time whether connected to a network or not. I've found nothing glaring to me in an enourmous ProcMon SysInternal boot-time capture, but I wasn't really sure what I was looking for. One suspicion I have is that software-install group policies that refer to a network path on a decomissioned server are at fault.

However I've created a test OU and turned off those policies, and the only one claiming update is readily available. Is there any way I can more closely monitor boot-time semiphors? Or Boot-Time GP processing? Turn on verbose messages about what is actually happening during the "Please Wait" screen. In my case, some old GPO-based installs were still being applied to some client machines.

Whatever is happening, flipping this registry setting to turn on verbose status messages should aid troubleshooting. We have the same problem with many Win7 Ent machines, but a different cause. When the repository gets big above MB then the Please Wait screen is shown for minutes. When disabling the "Windows Management Instrumentation" service winmgmt , then the problem disappear. There is a hotfix from microsoft that stops the WMI from running a full check on each bootup.

That is too heavy procedure in business enviroment where you have many thousands workstations. If Network Location Awareness Service startup disablation is the key result in Windows 7, not having "Please wait" states anymore, it would be easiest way to configure this service settings with Group Policy.

We have had this issue across a number of machines and we found a fix for it, I've put together and guide with all the files you'll need here:. I had this issue with a customers computer after a fresh install of Windows 7 Home Premium when trying to boot into safe mode. It turned out that the issue was pending updates that had apparently installed in the background and needed to perform pre-logon action. Due to the boot into safe mode, they could not finish configuring and caused the freeze at "Please Wait Sadly I had booted into Safe Mode by changing msconfig so I could not seem to boot into normal mode.

I waited about 15 minutes at the "Please Wait After restarting normally it failed updates, so I just re-installed updates and it went back to working normally. Moral of the story, just wait! Then boot into normal mode and run Windows Update to see if it was attempted updates causing the "freeze". I had a similar problem at work. We had migrated to a new domain controller.

Some computers started hanging at the "Please Wait.. We did everything people posted here: disabled NLA, enabled verbose logging, disabled all third party services and startups in msconfig, removing and readding to domain, etc. No success. All we know is that if its on the network hooked up to lan it hangs.

Remove the lan cable or remove the computer from the domain then it boots up fine. For us we got an error window instead of the "Please Wait" message that looked like this.. BroadCom installs them with some products as well but to date, haven't had any issue out of them.

It's February and I still see this issue a lot. So glad you created this KB as it helped me fix this bug after 3 months of extensive research. This was even happening with brand new images of windows 7 with SSD's in a domain environment.

Sorry it took me so long to reply. I have already tried everything you had suggested. I spent an hour or more disabling services and rebooting. That did nothing. The next thing I started doing was disabling services. I disabled everything that wasn't microsoft supplied. Then I disabled pretty much every service that was set to automatic.

Every time I rebooted, the system came up quickly without incident. I began re-enabling services and rebooting to see if any one of those caused the problem to come back. The only time the problem came back was when I re-enabled the NLA service.