No problem with Command Prompt or Powershell in 18334, here, Kari. Perhaps you are speaking of something else, however, as opposed to just opening these and using them as an Administrator (appears that way atm). Good luck! Build seems very stable here, but as I say we may not be testing the same things.
No, it seems normal, shutdown is fine--however, it's still buggy at least on cold boot. Yesterday I got nothing but the usual spinning dots, but the boot progressed no further--unique and unusual--but no boot until I did a manual power off and a normal reboot--at which point it booted properly. Every once in a blue moon I have some kind of similar problem with a cold boot, and that's been the case for awhile--pretty sure it's a build bug--I believe the build notes to this build or the previous mentioned the possibility of having to boot twice sequentially in some cases. Seems related to the reserve-space approach they believe has some kind of merit.
Can't help but notice the obvious and observe that lots of folks are throwing bunches of third-party software in between their hardware and the Windows build they're testing atm. Seems like a natural incubation spot for problems here and there. Just saying...should be a first assumption, eh?...
I also ran into the no cold start last night...first time I can remember it happening. Had to have a hard on-off switch shut down and then finally pulled the plug, re-plugged and it started. Also had a very long shutdown the first time I restarted after the install. These are not features I want in a system.
WEK
I am NOT talking about Command Prompt opened as administrator. I am talking about recovery environment Command Prompt, selecting Command Prompt in Advanced Startup options as told in Option Two in this tutorial: Open Command Prompt at Boot in Windows 10 | Tutorials
Kari
Hi thereCan't help but notice the obvious and observe that lots of folks are throwing bunches of third-party software in between their hardware and the Windows build they're testing atm. Seems like a natural incubation spot for problems here and there. Just saying...should be a first assumption, eh?...
Windows with nothing else installed is not particularly good for testing - the idea is to see if the build works in "normal use" -- just booting up and testing something like file explorer isn't really good enough.
3rd party software can mean all sorts of things - but basic standard things like backup / restore, virtual machine software, networking and Internet should be OK as a reasonable test bed as should email and some office stuff. I agree weird specialized gaming / gpu software etc probably isn't appropriate at this stage for skip ahead builds though.
Cheers
jimbo
Anyone else getting errors in Feedback Hub, says there is an update but when I click it to update it gives me an error also says Im signed out but when I click sign in now it asks me to sign out of my account !!
Totally agree with you there jimbo, it's not only 3rd party apps though. A couple of years ago I remember installing an Insider build which deleted a few apps I had installed. It had the decency to leave me a log file to read though and one app had been removed as it was from an unknown author. That app was Microsoft Money, go figure.
Quote
