Windows update fix Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX] "IsConvergedUpdateStackEnabled"=dword:00000000
Technical Preview Technical Preview for Consumer Technical Preview for Enterprise Can I take from this that the "for Consumer" edition is what used to be called Pro? If so, that's pretty weird, since the "base" edition is obviously "for consumers" too. The base edition is arguably the edition for (most) consumers. It's too bad that MS is still going to have two consumer editions. Continued termsrv.dll nonsense, etc.
No. Technical Preview = Pro Technical Preview for Consumer = Core Technical Preview for Enterprise = that is well..., Enterprise (included only for completeness)
This issue can be solved by creating a new user account. --- Is there anyone experiencing random reboots with a notification because of broken lsass?
boril, I am very thankful for your help and links. I spent 45 minutes following all links, ran all elevated powershell commands and command prompt commands manually. All ran successfully. Ran that tweaking.com tool twice. Ran the MS troubleshooting tool and it found and fixed an error. Ran all elevated commands again, followed every single step. And not a single Metro app runs. Trust me, I tried over a dozen of them this time. They all just display their normal background forever and nothing happens. I'm starting to wonder if MS has forcefully stopped us from using Metro apps without an MS account. It is now officially confirmed that there are no methods to fix this pile of garbage, sadly. And still receiving BSOD every second or third boot. EDIT: Odd, I am getting notifications from metro apps now in notification center tray. Yet those same metro apps producing the notifications still wont start. Some progress, I suppose. I will try creating a new user account and see what happens. EDIT2: Lovely. Can't create new user accounts without metro working. Hmmmm... I'm actually starting to wonder if this Metro/Modern is some sort of disease, it certainly is spreading.
You can run cmd as admin and use "control userpasswords2" without quotes (no space in userpasswords2). You shouldn't delete your current account at least before you'll transfer all the data you need.
Everything seems to be working now on my laptops and the one desktop that I have running this version of Windows. Still have a lag on the one laptop that has NVIDIA GO 6150 but I guess there is no driver for Windows 10 and there will never be one as I see it. Its a HP DV2310CA laptop and there is only drivers for it on HP site and it is for Vista x32 and x64.
Conclusion: - created 3 new user accounts - live tiles show new content, like news reader, yet wont open news reader - finally gave in, created my 1st ever MS account Guess what? Zero Metro/Modern apps work. None of them. I thought for sure MS account would work. It's ironic because for the past year or so I have always done everything to remove metro apps and hide any trace of it. And now when I want it to work, no such luck. This time when I clean installed 9901, first thing I did when I got to the desktop was tried to start a few metro apps. And they failed. But at least it rules out that it has nothing to do with my settings or additional software. This is KMS activated by MTK, so it's possible KMS kills metro. But as noted, you can't change product key now without metro working. Command line options are blocked in this build. I have no ideas left to try and have now put well over 12 hours into troubleshooting issues with this build. Time to forget metro ever existed and move on, desktop all the way.
That's sad, cause i ran into that problem too and used to workaround it with new account, apps seemed to be run in background, but didn't start. But now i'm stuck on lsass problem anyway and don't know where to go. 9888 had explorer bugs and i'm not sure if 9879's fixes can be applied. 9879 had an explorer and print spooler bugs and i don't know if it's fixed for now. 9860 was pretty stable. It's not a big deal to jump to an old build, you just need to run setup in compatibility mode (Windows 8).
I'll be quite honest, I went back to 9879 yesterday and it was like a breath of fresh air. There have been two explorer.exe patches in WU over the past week. I don't think they could be applied to 9888 though. GDI leak is still there though but there are workarounds to ease up on the leakage.
Than i'm probably not gonna jump on it, if explorer bug is still there, since 9888 is the same and doesn't have printer spooler bug.
To all of you having issues with 9901 is this clean installs or upgrades? I have one system with a clean install and this is easily the best build so far. My laptop has been upgraded to every build since 9841 and I think it's starting to cause issues, but I bet a clean install will fix that too, but even with the issues it's STILL better than that 9879 trainwreck.
I did both clean install and update, it's still the same with 9901. More like hardware-connected seems to me.
I mainly do clean installs only. Only tested once with the 9901 build an upgrade from 9879 and faced a lot problems. Did a clean install after LLF the HDD and still faced a lot problems! Used the Mega download from post #1 for it. Downloaded the ISO from Paul's Jukebox Link and did an LLF for the HDD and a clean install again and still face some some problems. The Major problem is that I couldn't install/add .NET FX 3.5 with .NET Framework 2.0!! That's needed for some Tool software I use and also for Moborobo which I could use for all different Smart Phones and Tablets we have in my company, not any other Software could do that! A PIN Code could NOT be created, is an other problem! With the last, now used install I even created an new MS Account to get all features to run without syncing to my 'old' data from the other installs. Still no changes! 9888 was also an 'flop' for me and couldn't install at all. That said, I think that I'll go back to 9879 sometimes the next few days or simply wait for the next 'official' release from MS itself of the next (supported) build.
Oh trust me I know all about hardware connected issues. X99 chipset rigs BSOD with any GPU in an X16 slot, put an AMD GPU in an X8 and it's fine, go figure....