Windows 10 installation stuck on windows logo screen

Hi.
It freezes at the spinning logo, right?

Have a good day.
Peter.

I ask, because I have a Supermicro motherboard which does exactly the same thing. If you try to disconnect it from the power, like completely (I know it sounds strange) then wait a few seconds and plug it in again. Turn it on, and you should get the desktop. If not, try and do it again. When you get in, please follow these steps to install the ME driver:

"Please follow the steps below:


1) Turn off the system completely, and turn it back on, you should be able to get back into the OS.

2)Download the following driver and extract it:

https://downloadcenter.intel.com/download/22655/Intel-Chipset-Device-Software-for-HECI

3) Open up Device Manager

4) View >> Show hidden devices

5) In the main window, expand System devices and look the device written exactly as "Intel(R) Management Engine Interface"

6) Right click on entry >> Update Driver Software

7) Click on "Browse my computer for driver software"

8) Click on "Let me pick from a list of device drivers on my computer"

9) Click on "Have Disk..."

10) Click on browse and navigate to where you extracted the file from step 1, then go to 'SPS_MEI_NULL_DRV_1.2.3.2003\All\patsHECI.inf'

11) Click Open >> OK >> Next >> Close

12) Restart the system

13) Go back to Device Manager and make sure you see "Intel C600 Series Management Engine Interface – 1D3A" and not "Intel(R) Management Engine Interface" in the hidden devices "

Source: http://www.supermicro.com/support/faqs/faq.cfm?faq=22744

I hope this works for you. I spent many hours trying to figure it out, when I found this solution.

Have a good day.

1. Presumably you're using the Windows Media Creation tool with the USB flash drive containing the Win 10 setup files, right?

2. You obviously have a working PC. Is that the Z170 system on which you want to install Win 10?

3. Assuming it is, does the current boot drive contain the Win 10 OS?

4. So how are you planning to install Win 10 using the OS installation media? Are you intending to fresh-install the OS on a new drive? Or are you planning to update the present OS on the system? Provide some details as to your intention(s).

5. If the Z170 system is "virgin" in that it doesn't contain a working OS, tell us something about the drive on which you're planning to install the Win 10 OS. An SSD? Disk capacity?

6. Do you plan to install secondary drives in the system as well?

You get the point, right? Just give us a clear picture of the system & components you're working with and what your specific objectives are so we'll be in a better position to provide you with specific guidance that you can consider.

It's really difficult to diagnose the problem from this distance without laying my hands on the PC.

What's ominous is your opening remark that the "usb wasn't working". You're referring to the Windows Media Creation tool that contains the Win 10 OS setup files, aren't you? What exactly do you mean when you state the "tool" "wasn't working"?

Presumably you booted to that USB flash drive "tool" which should have opened up the Win 10 OS setup process. Are you saying that failed? What PRECISELY happened? You never reached the opening Win 10 setup screen? What?

You then indicate (I think) that you were able to install the Win 10 OS setup files on a DVD, but that too failed. Is that what you're stating? Again, what PRECISELY happened during the boot process? The same as above?

Are you certain you were booting to the Win 10 installation media?

When you say your proposed boot drive, the 250 GB SSD has been formatted, is it MBR or GPT partitioned?

You obviously have a working PC. Can you install the Samsung SSD as a secondary drive in the system and test it with Samsung's Magician program just to ensure there's no problem with the drive. You've checked to confirm your SATA controller mode is AHCI enabled, right? That's the default so that should not be a problem.

(I'm always suspicious about a new motherboard being DOA. It's a rare event in my experience. Most of the time it's something else that's causing the problem - not infrequently user error/mistakes involving the connection of components and system misconfiguration errors, etc.)

1. It's a difficult problem to diagnose from this distance since the problem(s) you describe could arise from multiple causes.

2. I'm unsure why you mention the possibility of a "damaged CPU". While it does occur it's a rare event and virtually every experience we've encountered with such was due to user error while the user was attempting to install the processor in its socket. Intel has a diagnostic program to test its CPUs but of course you need a working system to employ it - Intel Processor Diagnostic Tool (available for download).

3. Under the present circumstances as you have explained the situation I believe the only sensible approach at this time is to "start over" as it were.

The basic approach would be along the following lines...
A. Get inside your desktop computer case (after disconnecting the A/C plug from your wall socket) and determine that the CPU, heat sink, memory modules & graphics card are properly seated and all connections appear secure. Remove (disconnect) all peripheral devices including all HHD & SSD drive(s), optical drive(s), sound card, etc. Disconnect ALL storage devices, printers, and any other devices connected to the machine.

B. So that all you'll be working with is your motherboard, processor, heat sink, RAM, graphics card, power supply, keyboard & mouse. Better yet, should your motherboard have onboard graphics capability, disconnect your graphics/video card from the system. Just ensure that if in case there is a BIOS setting for onboard graphics display that BIOS setting is enabled since that setting is frequently disabled as the default setting.

C. Reconnect your A/C cord and power on the system. What happens? Do you get a "normal" screen display? No error messages or strange notations from the system?

D. Can you access your BIOS/UEFI without any difficulty at this point and review the CMOS-BIOS settings? In particular, ensure that the SATA controller mode is set to AHCI (which should be the default setting). Check the hardware monitor/PC Health in the BIOS to determine that all temps are within normal range?

E. Assuming all is well at this point leave the system powered on for the next hour or so, checking to see if anything untoward shows up. Using your reset button, try powering down & up a few times to determine if there are any problems there.

F. Now you can install your graphics card in case it hasn't as yet been installed.

G. Should all appear well at this point this is an indication that there's nothing wrong with the basic components of your system. While not absolutely definitive this is so, it's a very strong indication that something else is amiss.

All this, of course, is to rule out at least to some degree) that the problem is not hardware-related insofar as the basic components currently installed in the PC.

Finally, install any BIOS update.

H. Presumably you can connect your SSD as a secondary drive in your working system. Do so and check out its health with Samsung's Magician program. Presumably you have or will be initializing that drive to the MBR partitioning scheme.

I. Install the SSD as the primary boot drive in your Gigabyte Z170 system and boot to the Windows Media Creation tool flash drive containing the Win 10 setup files. Hopefully you'll be able to fresh-install the OS onto the SSD.

I just don't see any other practical series of troubleshooting steps at this point but perhaps you have some other ideas.

Glad to hear that the problem was properly diagnosed and turned out to be a defective processor that could be RMA'd.

Presumably the Intel i7 Skylake 6700k CPU was fairly new in your system. How old was it?
And is it your impression from the technician's report that the processor problem was apparently the result of one kind or another of a manufacturing defect?
Or did he conclude the problem had (or might have) resulted as a result of some other issue?

Would appreciate your response to the above.