Jump to content


gopi8883

After Deploying Windows 10, PC struck on "Why did my PC restart?" Page

Recommended Posts

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.

WhyDidMyPCRestart.thumb.png.1394467e5cbaf463efa20ca9f1429fd9.png

Thank you,

Share this post


Link to post
Share on other sites


Hi,

I am doing a manual partition using the below steps before i start the task sequence

STEPS before booting from USB flash drive:

Diskpart

Select 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=c

Format quick fs=NTFS (Format primary partition)

Exit
 

Share this post


Link to post
Share on other sites

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 GPO

The “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. 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.

 

Share this post


Link to post
Share on other sites

It may be worth disabling part of your task sequence if you have not already so you are only putting an O/S on to the machine which would allow to further narrow down the root cause of the problem. 

 

In my case a task sequence re-order eventually sorted the issue out for me. 

 

 

 

 

Share this post


Link to post
Share on other sites

Thank you for your response. I already tested that. 

This issue happens only in the send half of the task sequence i.e., after the "Post-Delivery Configuration" Group. (Shown in above task sequence)

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

It was Group Policy - apologies to Gavin1973 who suggested that :mellow: That's why my first build worked until a reboot - policy hadn't applied to it yet.

Not sure which policy is doing this yet - we already had Consumer Experience disabled. 

Gavin - what's the private store key you changed?

p.s. Adding a reboot after the SCCM Client install brought back it displaying the TS progress box during the build.

Share this post


Link to post
Share on other sites

OK found 2 ways round this. Disabling the following group policy: 'Block launching Windows Store apps with Windows Runtime API access from hosted content'. We had set this on recommendation from a PEN test.

Also the following unattend settings have the same effect:

<settings pass="oobeSystem">

<SkipMachineOOBE>true</SkipMachineOOBE>

<SkipUserOOBE>true</SkipUserOOBE>
 

Note: These settings are deprecated in 1703 but work for now.

Share this post


Link to post
Share on other sites

This is the registry entry I had to move a round which was blocking me building the devices successfully.

Fix-SigninADFS - HKLM\SOFTWARE\Microsoft\PolicyManager\default\ApplicationManagement\RequirePrivateStoreOnly /v value /t REG_DWORD /d 1 /f

 

Share this post


Link to post
Share on other sites

Did anyone find a fix for this? We are experiencing this with deploying 1709 currently. 

Our setup:

 

  • UEFI + SecureBoot
  • SCCM CB 1706
  • Windows 10 ADK 1709
  • Windows OS 1709 Pro
  • Not using a Private Store. Store is disabled via 3rd party tool
  • Problem: Stuck in the "Just a moment..." blue screen after the TS completes. Eventually it times out/reboots to the "Why did my PC restart?" screen

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...