Some Surface Pro 3 owners are reporting problems installing the new Windows 10 10122 build

In what way is it a step backwards?

When it won't upgrade an existing machine, it's a step backwards to install everything new again.

It would be a step backwards if we weren't currently testing it.

its a preview... they ahve these previes to figure out these kind of bugs... if you want a clean build wait until official release

Wow, one build fails and apparently Microsoft should give up now.

That they give you a way to roll back to a previously known good configuration is a step backwards?  Um, no that's brilliant.  The condition is unfortunate, but that is the nature of testing.  Regression testing is not an easy feat and I can't imagine so with millions of lines of code.  Having said that, participation isn't required if you can't tollerate problems with pre-alpha/beta/release software.  It is better we discover this stuff now that when it goes RTM.  

If you are not impressed then why the hell are you using Windows 10...

My laptop is full of Intel and no issues :D , and I know alot of people with Intel and hadn't faced any problem

It isn't specific to the SP3.  10122 installed just fine on my SP3 and Lenovo W540.  Not so much on my Alienware 18 which happens to never have had a  problem with any prior build.  It hangs at 18% with the same exact conditions described for this "SP3" issue.  I've also tried all of the house cleaning and command line manual fixes suggested by Microsoft as reported by WC.com.  An odd issue, for sure.

installed fine on mine

This tip worked for me. My pro 3 is on the new build after this tip.  I was wondering if it had something to do with Visual Studio.    

Why would you do that? Have patience or suffer the consequences... and quit whining.

Two of our staff have SP3's with Windows 10 on it. Neither can upgrade, so it degrades our coverage too. So the "whining" here is relevant. Also, it's a bug that is reported and not expected by Microsoft. This is the point of TESTING software, after all. You act like Microsoft does not care Windows 10 cannot run on their flagship hardware.

indeed - i wish they would release teh 10122 ISOs instead

Gabe has already tweeted, ISO comes with Slow Ring release.

darn it...

i installed mine with the iso file, downloaded from a random site.  

Sounds safe.

lol, impatience makes us do many things

But you shouldn't use test software on coverage hardware.

Thanks for informing us of how to do our jobs. Can I swing by your work to give some advice too? /s

Exactly. If they're not going to test software on "coverage hardware" then what the heck is the point of their site?

I can't begin to tell you how many times I've tried this install. Every workaround, every possibility mentioned. While I'm frustrated that it's not working, I'm sure there will be some kind of fix/workaround (that works) in the next day or two. A clean install just isn't in the cards for me right now - I'd rather keep 10074 than spend two days reinstalling software. The good news is that I got rid of my Windows.old folder :)

So don't do it. 8.1 is fine

Testers cannot UPGRADE their current Windows 10 Preview, which defeats the purpose of giving feedback. If you are nixing a part of your subject pool, it is not "fine" as you say.

Gets to 18%

just download the iso file, although its not officially released by MS.

Same here, gets to 18% (Copying Files 62%) then it just sits there and nothing happens.

Last public build is not 10074?

So, yesterday happened, lol. Yesterday build 10122 was released.

Yes, it is 10074. Must be an error. Nothing major

...

XD

10074 is slow ring, 10122 is fast ring.

Not a surface pro 3 but my HP stream 7 ran into a device power state bsod and had to roll back during the final stages of the upgrade from 10074.

Yeah, gave up on mine last night. Nothing worked. Hoping for a speedy fix!

Not sure if it's new in this build, but Xbox app now lets you do (Win + G) to open a screenshot and record menu in games. Tried it in Minecraft, works well.

Happened in last one, at least I could see it on my SP3. But I play games on it without a keyboard attached so couldn't try it out. Will have to get one of our guys to do a little piece on it.

Gabe gave that message in a reply to my tweet. I tried 4 times with the same result. Freezes at 18%. 65% of file copy then it locks up. 

Same here

I only got to 1%. Posted via my HTC One (M7)

not only issues with the SP3... also issues with other devices getting error 0x80246017   https://twitter.com/GabeAul/status/601080802793922560

I am getting the 0x80246017 error on my SP3 and 2 desktop PC.  

I'm getting stuck at 18% completion (copying files 63%) on a surface pro 1st Gen device.

Yep another SP3 here that can't install the latest build, tried five times and done all the workarounds and nothing so far has worked.

download the iso file man.

That doesn't help.

Huge issues with SF2 PRO too

What is that device, again?

Same exact issue on my SP3 I5 tried all suggested solutions

Only problem i had when upgrading SP 3 (i5/256gb) from 10074 was that i could not install drivers for the buttons and shortcuts (i.e. volume ++), but it fixed itself after a restart. Other then that, no issues.

Count me in as another SP3 that gets to 18%, reboots, rolls back to 10074.  I have tried the file clean up ideas and deleted all non esstential hardware.  No luck yet.  

Same here. Did a system reset back to 8.1, installed updates, then 10074, then finally 10122, all before installing any apps or restoring data, and that worked.

Installed on my i7 SP3... But this build seems really buggy in terms of app installs

Interesting, mine is an i7 as well.

OMG, timing. I almost let many of you convince me that it was ok and I was going to do it this weekend. And now I will go back to trusting my gut.... waiting for RTM.  

Im surprised this wasn't discovered prior to deploy. I would think SP3 would be a primary test device.

If we want to find the positive thing on all this, it's less whiny users can't use Windows 10 Preview, that means all these "TOUCH SUCKS ON WIN10, IT SUCKS. I WILL STAY ON WINDOWS 8.1" people will not be heard in a while and their crappy feedback. How can we complain about it? I think it's better. sometimes it feels some people should stay away from these Previews and how they pretend it's a final build where no bugs or problems or uncomplete stuff will be found.   I of course wouldn't mind if Windows 10 just destroyed these SP3 and other devices, burning them to small ashes.  ^____________^

SP3 I7 here, had connectivity issue with Windows update, then all was good.   I hope the rest of you get a workaround soon!

This is not isolated to SP3 Pro only - I have a Dell XPS 2720 all-in-one and I'm facing the same issues with identical error codes. On the other hand, my XPS 15 laptop got upgraded without any problems.

Downloaded an ISO and did a fresh install, worked fine for me after that. 

I downloaded the ISO for 10074 and did a fresh install from running the Setup file off a USB drive since my SP3 will not boot to a USB drive for whatever reason. Updated to 10122 after the previous install was finished. Only issue I ran into was setting up my Microsoft account. Did not want to allow me to log in with my MS account during the setup for 10074.

SP3 can only boot via USB key, drive or whatever if the thing has FAT32.  If it has exFAT it does not boot.

Yeah i have had the exact same issue.

Why would a person install a preview OS on a 1000 dollar unit? Buy a cheap POS laptop for that or use an ok machine for that.

For this reason XD 

Yep SP3 here as well, can't install. And since last night I figured it was something wrong with my WiFi

Experiencing similar issues with Dell Venue 8 Pro - 10122 consistently fails during either downloading the update in the first place or preparing upgrade and never reaches reboot.    Receiving a number of errors also from Windows Defender and Windows Update itself.    So yeah looks like the only way to get this build now is ISO.   And from some of the other feedback the question becomes - do you want to go there at all...or are we going to quickly see another build like the 10056 to 10074 cycle.. What is concerning to me and I think others have experienced - Windows 10 seems to install / upgrade extremely easily on traditional desktop systems - but is a complete pain in the ass on tablets & phones.  Makes me wonder how much focus MS has right now on those platforms.  

Well looks like I have to wait a few more weeks to have the build 10122

How did they not see this? WTF do they use in Redmond? iPads?

It's a bit of a worry - my thoughts too....

perhaps it  worked on their ones

I tried 4 times, and same error, even after clearing all the inf files. On the 4th attempt my SP3 actually overheated and shutdown, back on 10074 now.

Installed fine , I liked it , but why did they remove full sized start screen -_-

They didn't.  You need to look into the start menu options.

I had this problem. I tried repeatedly and it kept occuring. I fixed my issue by running CCleaner (and checking the "Old Windows" checkbox). Then I deleted the Windows.Old folder by going into advanced security and assigning myself as the owner and then deleting. After that I was able to update fine.

I had the issue.  Just reverted back to previous build.  I have a Venue 8 pro that isn't even getting the update offered.

I get stuck at 18%. Then I have to do a hard shut down but it reverts successfully so ill wait till they fix it...

Some users are reporting success with this fix. I havent tried it yet. http://blogs.technet.com/b/ems/archive/2015/05/21/installer-stuck-at-18-...

Link doesn't  work.

Try it now. I fixed it.

This is a working link, unless it gets mangled somehow by posting it here. http://blogs.technet.com/b/ems/archive/2015/05/21/installer-stuck-at-18-when-upgrading-from-windows-10-10074-to-10112.aspx Following these instructions cleared up the problem and allowed me to get 10122 installed on my Surface Pro 3.

You don't need that program to do that. That is a different way of doing the same fix that the release notes state of the new build. you can do it by doing a disk cleanup of system files and selecting drivers. IT was suggested to do that on any windows 10 machine upgrading to the new build.

Neither worked on my i7 SP3. Still freezes at 18/62

Someone tell me when a fix for the 0x80246017 error code that worked for many people turns up. (btw, I didn't modify my registry to get builds early, so nobody tell me to change the keys back to normal, since they were always like that.)

righto. sign me up.

SP3 i7, updated from 10074 to 10122 using the baked-in Windows update tool.

This is not a new issue. The affected users have had this problem upgrading every internal build beyond 10074 including a few builds beyond 10122. It has nothing to do with Intel. If you look at your setup logs it has to do with Driver Injection.

Except it is a new issue for some of us.  I have installed every preview build since they first started relasing them on my SP3, wihout a single problem.  Now with this update I cannot get it to install no matter what "fixes" I try.  Try not to lump everyone into a bucket when they clearly may not fit into that bucket.

No lumping. If anything I'm way more frustrated than you because I've been stuck for about a month. I just meant that telemetry should have shown that this was problematic on every build since 10074, so I think it's kind of ridiculous that they released another build to Insiders without addressing it. Sorry for the confusion.

https://twitter.com/GabeAul/status/601494238182899712 New possible fix for SP3 owners

After using the Disk Cleanup... Cleaning stuff with CCleaner and deleting the Folder Windows.old
I'm still unable to install the build 10122 :(

Found it impossible, eventually forced to clean install 10041 iso, update to 10074, then to 10122. Has left me with a couple of apps in limbo, can't install fully or remove.

Buttery smooth.

This issue can be fixed quite easy: disable bitlocker! (e.g. by running msconfig, untick bitlocker in the Services tap, reboot) the "rundll32.exe pnpclean.dll,RunDLL_PnpClean /DRIVERS /MAXCLEAN" is useless. That was indeed another issue but not related to build 10122. Be carefull when installing build 10122 as the Surface Pro gets quite hot. I even had again the temperature gauge and the device shutting down during the install.  The second attempt worked after I let the device cool down a bit. Blaming MS for: a) they either don't know about this issue and solution or don't inform us about it b) they are still not able to construct hardware. This Pro 3 is now my second Surface. I also own the new Macbook. This is really one piece of hardware to like and it is definitely light years ahead any MS device. It is small, light, surprisingly fast, very long battery lifetime vs the Pro 3 is ugly, too thick, heavy, battery not really lasts long - and it is getting hot and stops working.