Announcing Windows 10 Insider Preview Build 16226 for PC Insider

EdTittel said:

I, too, cannot get .NET Framework 3.5 (and older elements) back on my Dell Venue Pro 11 7139. Same error code as the earlier poster with the same problem. Here's a screencap:
Attachment 140687
My biggest problem with this comes from a handful of utilities -- including Core Temp/8GadgetPack, RAPR, Secunia PSI, and no doubt others -- upon which I rely. Alas, they apparently rely on older .NET versions, and won't work without said support loaded and running. Ouch!
--Ed--

PS: I posted to Feedback Hub on this, including a trace of the powershell stuff shown running and failing. Hopefully, that will help them. We'll see how long this sticks around...

I tried *everything*! It's not going back on... So far hasn't impacted anything I'm running, since the AMD Crimsons no longer require .net 3.5 (the AMD Catalysts would not install without it--even if you had the 4.x versions installed.) The last time I had this problem I was able to overcome it simply by manually installing it from a disk source (DVD or mounted .iso.) Not this time.

hawkman said:

Hi Walt,
did you read the change log Under IT Pros.
SMB1 automatically uninstalled

Roy

Thanks Roy,

Yes, I did read it and that's why I uninstalled it...;) Here's the quote:

As part of a multi-year security plan, we are removing the SMB1 networking protocol from Windows by default. This build has this change, however the change only affects clean installations of Windows, not upgrades.

I was doing an upgrade...;) Which succeeded without difficulty, fortunately. They go on to say that in future builds the client would be uninstalled by default if present, but in 16226 upgraded, if SMB 1.0 was present in the upgraded build it would still be present after the upgrade to 16226. At least, that is how I understood it...;) Since I uninstalled .net 3.5 ahead of doing the upgrade I figured it wouldn't hurt to go ahead and get rid of the SMB 1.0 client at the same time--just in case!

Anyway, now I can't get .net 3.5 to reinstall even through the manual DISM method--which always worked before. Go figure.

EDIT: I just noticed that 16226 turns on fast-startup (under the Shutdown options) as well as turning on hibernation! Neither was turned on in 16215, so these were turned on as per this build and not carried over from the last one!

badrobot said:

@sneekez , I restored back to 16215 and trying the ISO I made right now by doing an in-place upgrade with it.





*********UPDATE: *****************

The ISO worked.
It only to 24mins to complete the update.

Good deal! Glad to hear it. I'm still seeing some peculiar stuff with these builds in some D3d 7.x/8.x games--that ran beautifully under Win10 prior to the 10563 CU build. I know that like me you appreciate your games (the finer things in life, eh?...) and thought I'd ask if you were seeing something similar in 16226.

Hi guys, just installed this update and now my keyboard seems to cut out when I'm typing. It seems laggy as well. Any ideas? Will have to roll back as computer is unusable

CountMike said:

Because of this and I did have .NET 3.5.
"If you have the .NET 3.5 Framework installed, updating to this build may fail and roll back to the previous build. As a workaround, uninstall .NET 3.5 before trying to update to this build and then reinstall .NET 3.5 after you update to this build. For more info, see this forum post."

Did I read right that you said you couldn't reinstall 3.5, either? (Hoping you've discovered something here that I've missed!...)

crazyazz said:

Hi guys, just installed this update and now my keyboard seems to cut out when I'm typing. It seems laggy as well. Any ideas? Will have to roll back as computer is unusable

Try opening up the Device Manager, locating your keyboard drivers, and uninstalling them (do *not* remove them--just uninstall them.) Then reboot and see if that helps--they will reinstall automatically. All I can think of atm.

Here is the .net 3.5 Reinstallation solution, folks!

Run msconfig.exe, boot into safe mode with networking, and open Programs and Features, and you know the rest--.net 3.5 will install perfectly, first time. Then reboot normally.

This is one of those "Gawd, I could have had a V8!" forehead slapping moments! I wish I could say I thought of this--but I got it somewhere else and figured I'd share it. How simple--it's embarrassing...