Windows 10 Insider Preview Build 17101 Fast + 17604 Skip Ahead Feb. 14 Insider

f14tomcat · 15 Feb 2018

darkside said:

Attachment 177284In that case, I'd like some help with this. Resetting the windows update component didn't work

That looks like it was from last Saturday, the 10th. Way before this build came out. Possibly the last build, 17093. What was it trying to install?

darkside · 15 Feb 2018

I was trying to install build 17093. If I hit retry now, it'll return with the same error message. I also tried the sfc /scannow and dism cleanup commands. Both reported that everything was fine

f14tomcat · 15 Feb 2018

darkside said:

I was trying to install build 17093. If I hit retry now, it'll return with the same error message. I also tried the sfc /scannow and dism cleanup commands. Both reported that everything was fine

And you tried this: Reset Windows Update in Windows 10 Windows 10 Tutorials

darkside · 15 Feb 2018

So the first time I ran the .bat file, it closed when it was deleting some logs from the windows directory. I thought this meant that it was finished, so I rebooted. Same result.

I tried the second time and the same thing happened

magilla · 15 Feb 2018

Wynona said:

Magilla, if you have a WinPE key, you can boot your computer with that and it will try to repair boot, but won't work. The only thing you can do is get it booted.

I used macrium pe and loaded it then went back to reboot system and it booted. What’s with this - any clues?

blackroseMD1 · 15 Feb 2018

Decided to try 17604 on my Surface Pro 2 and now it's stuck in a boot loop. Guess it's time for a clean install of FCU.

steupz · 15 Feb 2018

17604 breaks multi monitor on my old system (Intel HD3000)
17101 works well on the Surface

Wynona · 15 Feb 2018

magilla said:

I used macrium pe and loaded it then went back to reboot system and it booted. What’s with this - any clues?

No clues here, Magilla. I still can't boot without WinPE (made with Macrium).

blackroseMD1 · 16 Feb 2018

Hmm, I keep getting the following message in Event Viewer after an app crash which is then followed up by dwm.exe crashing pointing to dwmcore.dll.

The description for Event ID 2 from source NVIDIA OpenGL Driver cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

The NVIDIA OpenGL driver has encountered an out of memory error. This application might behave inconsistently and fail.

Is anyone seeing any similar issues? I'm about to run DDU and try an older version of the GPU driver to see if it fixes it. I just find it odd, especially since this never occurred on the previous build with the same driver version (390.77).

slicendice · 16 Feb 2018

Today I made a final attempt to getting Build 17101 installed.

First I tried normal WU
Then I tried upgrading from ISO
Then I tried Clean install from ISO
Finally I tried repairing the install

All methods failed with same SYSTEM THREAD EXCEPTION NOT HANDLED

The final repair attempt ended up in a boot->memory dump loop that occur straight at boot with same exception code as before.

I give up...

EDIT: Almost forgot...tried this in Hyper-V, VirtualBox using different virtualization methods and in VMWare. Same results.