This probably happened after you went thru setup, activated your wi-fi, or plugged in a network cable, then put in your user name and password, etc.etc. And as it went to the next phase of 'setting up', you got the 'just a moment' error. This is a normal error, happening with lots of people). I have found this to be a problem with Hardware Identification, during setup.Here's what I have done, to make it happy and finally get past the 'just a moment' stuck screen.1. Disable your Wi-Fi or unplug your network cable if so setup.2. Remove any USB device, keyboard, mouse, printer, usb drive, etc.then reboot computer and see if it gets past the 'just a moment' screen. It worked for me on a few laptops, I have setup for various offices.Once it boots, if it does, and you get to your desktop.
Then turn on you wi-fi and have it 'configure' itself. Make sure it works. Then reboot computer.
If that works. Then connect any USB devices you have, one at a time, wait for them to setup, then reboot after each one is configured.that worked for me.good luck-sapphire.
Hi there, I know the exact solution for this particular problem.If you bought a new computer and stuck on 'just a moment' then it clearly indicates that u immediate unpack your new computer. Start plug in things like keyboard, mouse or so on. This action is very dangrous for a new window start up for your new PC since this is your first time run the system. Solution for whoever encountered this problem.1. Turn on PC, CTRL+ALT+Delete. Look for option to reset PC.2. Reset the PC, it will re-install new window.
(Make sure you unplug all external hardwares such as usb, mouse, keyboard, and so on, left only the Charger on)3. After roughly 1.5 hours the PC will work as a charm.Thank me later.
Sorry if this is in the wrong thread never used this before, I have a dell insprion 15 laptop, I recently cleaned the drive fully. Since this takes several hours I let it run over night while I slept, I woke up in the morning and a screen had popped up mentioning pdf files files. Me being half asleep and not fully understanding it I just clicked the first option, it rebooted and began to install windows again, I believe it fully installed, I got to the next stage of clicking timezones etc etc for the setup, after that it goes to a blue screen and says 'just a moment' and eventually resets itself and says my pc struggled to start we have a update which we think will help, so I click okay, type in my WiFi password but then it gets to the 'just a moment screen' rinse and repeat.
I've tried another reset 2 times from the automatic repair options it's got to the exact same place everytime. Sorry for the long message didn't want to forget anything that might help my case.
Any help is appreciated. Turn off the laptop.2. Turn off your WiFi, or take the laptop to an area where there isn't any WiFi. (If connected via Ethernet, unplug it.)3. Turn on the laptop.4. Download winning eleven 2019 for pc. Once it fully loads, then turn on your WiFi again.It should work now. Sometimes (especially in 10) updates, including those that come after a reset, can get the computer stuck.
It happens when an update fails, for whatever reason, and the device continually tries to get it to install over and over. Leaving you 'stuck'. Until you take away its ability to continue trying the update, hence the no WiFi, then it should load. Turn off the laptop.2.
Turn off your WiFi, or take the laptop to an area where there isn't any WiFi. (If connected via Ethernet, unplug it.)3. Turn on the laptop.4. Once it fully loads, then turn on your WiFi again.It should work now. Sometimes (especially in 10) updates, including those that come after a reset, can get the computer stuck.
It happens when an update fails, for whatever reason, and the device continually tries to get it to install over and over. Leaving you 'stuck'. Until you take away its ability to continue trying the update, hence the no WiFi, then it should load.Hi there, what do you mean exactly by fully loads, I've tried your steps, and I get to the stage where it wants me to add my time zone etc, and then the step after that asks for wi fi, I have clicked skip this step as I have no router on, after that's its stuck on a 'just a moment screen' however this time before my WiFi step, I got a screen titled 'why did my pc restart' with a list of a few instruction options, all of whichHave already been followed. Windows 10 came on this laptop.
Not sure if any of this helps. Just hoping I Dont need to by a new laptop as this cost me alot. Ok sit down and have a cup of joe and relax. First off windows restore and system restore can fail if there a bad drive or a virus. Windows also wont roll back if there no restoe points.
Also doing a restore most times is for a damaged windows or a bad update. To be able to get into windows and back up your personal data and then running the factory restore or replacing a failed hard drive. Most new dell and hp have a factory restore on there hard drive now. If you can boot into windows use a usb stick or online backup to safe your personal files. Then run the factory restore to put a clean image on the hard drive.
If the restore failes or takes hours your hard drive or other parts have failed or are failing causing issues. Do not make a windows restore usb stick at this time and use it. If you do you lose all the extra programs and drivers that are in the stock restore image.
Windows plain from ms will fit on a 8g usb stick.it has both 32 and 64 bit installers for windows 10. If your hard drive is still working most vendors now will let you make a bootable usb iso from the factory restore on the hard drive. If not dell may have a disk or a iso image that let you make your own restore usb stick.
If you can get into windows right now download and run hdtune see if your main drive shows any health warnings. If it a wd or seagate drive download and run there vendor diags. For the laptop memory. Power down and pull the battery check that the ram is lock in on the laptop then run memtest from a usb stick see if there are any issues.
For a virus start with malwarebyes then do a few free online virus scans from the big anti virus comp.
Hi,I am using a standalone media to install Windows 10 Version 1703 in my network. When almost the installation is complete, I am getting to see the page which says 'Why did my PC restart?' I tried to restart the PC but still the same page comes up. Its like Ia m struck here with no clue. I am connected to the network with LAN cable but still nothing happens. Please help me fix this issue. I even cant get to any other page, i wanted to check the log files but no way i can go out of this page.Thank you.
Hi,I am doing a manual partition using the below steps before i start the task sequenceSTEPS before booting from USB flash drive:DiskpartSelect disk 0 (0 being the disk to setup)Clean (wipe the disk)Convert gpt (convert disk to GPT)Create partition efi size=200 (EFI system partition)Assign letter=s (Any allowable letter)Format quick fs=FAT32 (Format the ESP)Create partition msr size=128 (Create the MSR partition)Create partition primary (Create Windows partition)Assign letter=cFormat quick fs=NTFS (Format primary partition)Exit. Hi,I had actually the same issue when deploying Windows 10 1703 into my environment.I have managed to rectify the situation which another blog refers to disabling the 'Consumer Experience' via GPOThe “Consumer Experience” is the default mode Windows 10 (including Enterprise) is shipped with. This mode, upon initial login of a new user, commences the automatic download of a plethora of (unrequested) UWP apps, thus filling the start menu with games like Candy Crush. I deplore this feature beyond anything Microsoft has done in the past. It cheapens the Windows experience and frankly, I think they should be embarrassed that this is included in their flagship product.
Windows 10 Stuck At Just A Moment
Fortunately, this feature can be disabled – but only on Enterprise edition.In my case this policy was not set and building the device into an OU in Active Directory where there were no GPO's proved successful but as this would not solve my issue I started to look at my build Task Sequence in SCCM.I finally discovered the issue was related to us requiring a private store and me setting a registry key and all I had to do was move this to last part of the build process. Glad I'm not the only one with this problem! We just updated a test TS with 1703 yesterday and get this error.Strangely the first build I did worked, logged in, all looked good. Then I rebooted and it auto-logged in as defaultuser - the screen would go blank but I could remotely access it. A few more reboots and the dreaded 'Why did my PC restart' appeared.I've since built the same hardware twice with no changes.
It completes but goes straight to the 'Why.' Screen every time now.It is definitely using UEFI. The drive is definitely C: - Group Policy does not apply during OSD so can't see it's that.Could be as simple as a re-order as suggested above so will probably add a reboot after the SCCM client. I will look at the unattend.xml and upgrading the ADK to 1703 next. I also don't see the TS progress any more, just get 'Just a moment.' Displayed and a spinning wheel.
I recently had this issue with my 1709 image. It was getting the 'Why did my PC restart' screen as soon as it was time for the task sequence to add the machine to my domain. I took Config Mangler's suggestion and added a restart in my task sequence right after 'Setup Windows and Configmgr', but before it was time to join the domain, just so I could get back into the PXE environment and get an error box.
Instead this actually fixed my issue and everything went through.(Don't forget to check 'The currently installed default operatins system' mark in your reboot.)I have the Microsoft consumer experiences turned off in the registry of my.wim if that matters.
Hello all.I am building my first Windows 10 Ent image build 1607. I installed it on a DELL Opti 7040, added drivers (although most of the drivers that Windows update installed were newer than the DELL drivers available), installed O365 client, installed all updates for Windows and office, installed InfoPath for O365, then booted into audit mode, ran the Win10 Decrapifier V2, removed any AD accounts that had been created during this process (I had added it to my domain) and then ran Sysprep without an answer file. I then used Clonezilla to create an image.One I boot the image, it gets stuck on the 'Just a moment.' I've rebooted repeatedly, gone into Computer Management and added passwords to the Admin account and activated it, I've deactivated the NIC port, sound card, etc but nothing works.Any ideas? Minus the decrapifier, this is the process that always worked for me with Win7, although with Win7 I did use a very simple unattend file.Thanks. Big Green Man wrote:kfberns wrote:It sounds like you took a new 7040 OEM, added / Removed software, then booted to Audit mode, then ran SysPrep - is that correct?Try booting into Audit Mode right away (Ctrl+Shift+F3) before selecting 'Use Express Settings' during your first boot. Then add / remove software, and finally sysprep OOBE.I just completed this last week without errors on a Dell 3040 / W10 ProOP said enterprise, so I don't think that's correct.OP, how are you deploying?
I had this issue when deploying with WDS, but I wasn't able to resolve it until I moved to MDT.I'm deploying using Clonezilla. It's a simple solutions similar to Ghost.
I only have about 70 computers in my environment so wanted to keep it nice and simple.Do you still have your pre-capture sysprepped image? This forum has a pretty detailed step explanation:State Restore1. Restart computer2.
Use toolkit package (again?) - Computer has been restarted. Initialize environment.3. Install Software Updates4. Gather (Gather what?) - Computer has been restarted. Publish all locally stored values back into the environment.5. Tattoo (what does this step do?) - Store some information about the deployment in the Registry to be able to collect them later using SCCM6. Install Software7.
Restore Groups (what does this step do?) - Restore any local groups if captured during the 'State Capture' phase8. Move State Store (what does this step do?) - moves the state store to a 'secure' place at the end of the task sequence so it does not get deleted.9 Copy Logs (what does this step do?) - it copies some logs (mainly smsts.log) to a network location if configured (need to set the variable SLShare)As for the black screen that sounds like a hang so you should look at the logs and report back if you see anything that points to the hang cause. Gather Logs and StateStore on Failure - See this as a Try.Catch block. It will ensure that the state store gets moved to a different location (mostly C:WindowsTemp) and the logs will be copied to a network folder.
It's mainly for error handling and will only execute if the last Action did not succeed. In regard to the 'why' it might have happened a reboot (that could even be the cause for the last error) so we need to initialize the environment first.1. Use Toolkit Package (again?
Gather (Gather what and why?)3. Move state store (what does this step do?)4. Hey @kfberns, I added all my software and updates, went into audit mode and then ran the Decrapifier to remove the apps. I had read that doing that would help ensure what the Decrapifier does would be rolled out to subsequent logins and not just for the current user.
I've honestly never used audit mode in the past when creating images.That being said, my image FINALLY did make it past the 'Just a moment.' Now I need to find out what, if any of the things I did helped.
I'm going to deploy this image on another 7040 and try to time how long it takes for the OOBE to finish without me doing anything, if it EVER does.Thanks for the input. We'll see how this goes.
I'm hoping not to have to make the image again. But I'll keep it in mind for future images for sure.
Kfberns wrote:It sounds like you took a new 7040 OEM, added / Removed software, then booted to Audit mode, then ran SysPrep - is that correct?Try booting into Audit Mode right away (Ctrl+Shift+F3) before selecting 'Use Express Settings' during your first boot. Then add / remove software, and finally sysprep OOBE.I just completed this last week without errors on a Dell 3040 / W10 ProOP said enterprise, so I don't think that's correct.OP, how are you deploying? I had this issue when deploying with WDS, but I wasn't able to resolve it until I moved to MDT. Big Green Man wrote:kfberns wrote:It sounds like you took a new 7040 OEM, added / Removed software, then booted to Audit mode, then ran SysPrep - is that correct?Try booting into Audit Mode right away (Ctrl+Shift+F3) before selecting 'Use Express Settings' during your first boot. Then add / remove software, and finally sysprep OOBE.I just completed this last week without errors on a Dell 3040 / W10 ProOP said enterprise, so I don't think that's correct.OP, how are you deploying?
I had this issue when deploying with WDS, but I wasn't able to resolve it until I moved to MDT.Pretty much my thoughts exactly. I use MDT and WDS and follow the same procedures as the OP with no issues. Usually takes about 20 minutes to deploy the golden image and have it accessible to use on a workstation. Big Green Man wrote:kfberns wrote:It sounds like you took a new 7040 OEM, added / Removed software, then booted to Audit mode, then ran SysPrep - is that correct?Try booting into Audit Mode right away (Ctrl+Shift+F3) before selecting 'Use Express Settings' during your first boot. Then add / remove software, and finally sysprep OOBE.I just completed this last week without errors on a Dell 3040 / W10 ProOP said enterprise, so I don't think that's correct.OP, how are you deploying? I had this issue when deploying with WDS, but I wasn't able to resolve it until I moved to MDT.I'm deploying using Clonezilla.
It's a simple solutions similar to Ghost. I only have about 70 computers in my environment so wanted to keep it nice and simple. Big Green Man wrote:kfberns wrote:It sounds like you took a new 7040 OEM, added / Removed software, then booted to Audit mode, then ran SysPrep - is that correct?Try booting into Audit Mode right away (Ctrl+Shift+F3) before selecting 'Use Express Settings' during your first boot.
Then add / remove software, and finally sysprep OOBE.I just completed this last week without errors on a Dell 3040 / W10 ProOP said enterprise, so I don't think that's correct.OP, how are you deploying? I had this issue when deploying with WDS, but I wasn't able to resolve it until I moved to MDT.I'm deploying using Clonezilla. It's a simple solutions similar to Ghost. I only have about 70 computers in my environment so wanted to keep it nice and simple.Do you still have your pre-capture sysprepped image? If so, does it load normally if you boot to it? Big Green Man wrote:kfberns wrote:It sounds like you took a new 7040 OEM, added / Removed software, then booted to Audit mode, then ran SysPrep - is that correct?Try booting into Audit Mode right away (Ctrl+Shift+F3) before selecting 'Use Express Settings' during your first boot. Then add / remove software, and finally sysprep OOBE.I just completed this last week without errors on a Dell 3040 / W10 ProOP said enterprise, so I don't think that's correct.OP, how are you deploying?
I had this issue when deploying with WDS, but I wasn't able to resolve it until I moved to MDT.I'm deploying using Clonezilla. It's a simple solutions similar to Ghost. I only have about 70 computers in my environment so wanted to keep it nice and simple.Do you still have your pre-capture sysprepped image?
Quick Navigation:.Help, Windows 10 Is Stuck in Resetting!As is well known, Windows 10 has become the newest Windows operating system and it is used by many users for quite some time because of its merits.However, in this world, no operating system is perfect, is it right? Windows 10 is not an exception. Tip: In addition to the issue of resetting Windows 10 stuck, some users report Windows 10 restart stuck on black screen. If you are bothered this, refer to this post - for help. How to Fix Windows 10 Reset Stuck Black ScreenIn many forums and blogs, many methods are introduced. Here, we will provide you with three reliable solutions to the Windows factory reset stuck problem. Solution 1: Restore Your PC with System Image BackupIn recent times, data protection has caught many users’ eyes due to many common factors, such as virus influence, system failure, mistaken actions and so forth.
Tip:. If the backup image doesn’t appear in Restore page, just click Add Backup option to add the backup to the interface. In MiniTool ShadowMaker Bootable Edition, the drive letters of some partitions are variational. Thus, please add the correct backup file according to partition size.Step 3: Depending on the backup version, you can make sure whether this backup task is the one you want to restore. Click Next to go to step 4.Step 4: By default, all partitions included in the selected backup file will be checked.
Then you can choose the partitions you want to restore. But here, as to system restore, all system partitions are necessary. Windows 10 System Image Recovery in WinREIf you have a system backup image which is not created by MiniTool ShadowMaker but Windows Backup and Restore (Windows 7), how can you fix Windows 10 stuck in resetting issue via the backup image? Follow the steps below.When Windows 10 reset fails, the computer can’t boot to the desktop.
In this case, you can go to WinRE (Windows Recovery Environment) to do the restoration.Navigate to Troubleshoot Advanced options System Image Recovery. Then follow the instructions to perform the recovery.Solution 2: Run Startup Repair by Windows Repair DiscIf you don’t have a system backup made by MiniTool ShadowMaker or Windows built-in backup tool, how can you fix Windows 10 resetting this PC stuck issue? Don’t panic.It is still easy and you can run Startup Repair to fix your computer by a bootable disc. Let’s look at the details.Step 1: You need to download Windows install files from the internet and then save it to a USB flash drive or a DVD.Step 2: After you get ready the installation files, restart your computer from the bootable disc.
In order to do the job, please go to your BIOS and set the USB drive or DVD as the first boot device by “↑↓” keys.Step 3: Then when booting into Windows installation interface, you can see there is an option called Repair your computer, then, click it to Troubleshoot interface.Step 4: Then navigate to Advanced options and run Startup Repair to fix the issue of resetting this PC stuck at 1, 8, 12, 33, 66, 99 percent.Step 5: Choose an account and enter its password to fix resetting Windows 10 stuck issue. Solution 3: Reinstall Windows 10If you are bothered by Windows 10 reset stuck on spinning circle for a long time, you try to repair it according to solution 2, but finally, Windows 10 factory reset failed again.In this case, what should you do?You can only reinstall Windows 10 so that your computer won’t get stuck at 1%, 12%, 33%, 66% or 99% when resetting this PC.
Please have a Windows installation disc ready and then perform an installation. Tip: Windows reinstallation will cause data loss. Thus, we suggest with MiniTool ShadowMaker Bootable Edition. Just get it from MiniTool ShadowMaker Trial Edition.When Windows 10 stuck on resetting this PC issue happens to your computer, don’t feel helpless.
Try the above solutions to fix this problem and then enjoy the smooth computer. How to Protect Your ComputerAs you know, system issues are easy to happen to your computer, for example, the aforementioned Windows 10 reset stuck black screen issue.In the second part, we advise you to restore your computer to the normal state with the system image backup. This way can help you to solve many system issues.Thus it can be seen that to create a system backup is vital. When Windows 10 factory reset stuck happens, the computer can run normally after system restore.If there is no such a backup, it is likely that you need to reinstall OS.How can you create a system backup to protect your computer? Here are the details.You can choose the professional backup and restore software – MiniTool ShadowMaker to do this work. Just get it from the following button.Step 1: Enter the interface where you can choose Local Backup or Remote Backup.Step 2: Navigate to Backup page, and then you see MiniTool ShadowMaker has checked the system-related partitions in the current OS. And you need to choose the backup destination, for instance, an external hard drive.As to system backup, we strongly recommend you to create an automatic backup by Schedule feature or use Scheme to create incremental backups for the changed and newly added data.Step 3: Click Back up Now to perform the backup operation.By means of system backup, no matter which system issue your computer encounters, like resetting this PC stuck at 1, 8, 12, 33, 66, 99 percent, you can restore the computer to the previous state.In addition, the MiniTool team also offers you another way to protect your computer.
Here MiniTool Partition Wizard is a recommendation since it supports OS migration to another hard drive.By this way, once Windows 10 reset stuck black screen happens, you can boot your computer from the disk containing the OS copy.Now, free download MiniTool Partition Wizard and install it on your computer.Then, begin to migrate OS to another hard drive by using Migrate OS to SSD/HD feature. Endless frontier new honor units. Bottom LineIs Windows 10 stuck in resetting? We have introduced you three ways in the above parts. Just try them one by one if the issue of resetting this PC stuck at 1, 8, 12, 33, or 99 percent happens.In order to protect the computer, you had better back up the Windows 10 on a regular basis with MiniTool ShadowMaker.When using our software, if you have any question, don’t hesitate to tell us. Besides, as for the suggestions, we are also appreciated. Here an email is supported or you can also choose to leave us a comment. Facebook.
Twitter. Linkedin.
Reddit.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |