Windows 10: Update 19405

I don't know how but after this update I can't power down. I have to use the switch. Ideas please

:)

 

Windows update_1900101 Windows 10

I haven't been able to install Windows 10 due to the following error: C1900101-20017. Any idea what this is and does it mean I'm out of luck?

 

SWE FILES WON'T OPEN ON MY PHONE AFTER 7.5 UPDATE?

SWE FILES WON'T OPEN ON MY PHONE AFTER 7.5 UPDATE? The browser says windows phone does not support this file type. I use to always open this file prior to the update.

 

Hello enigma, *Smile

This is a known issue in build 14905.

Announcing Windows 10 Insider Preview Build 14905 for PC and Mobile

Known issues for PC

• When clicking on the power button on the Start menu, it closes the Start menu without opening the flyout with restart/shutdown options appearing. As a workaround – you can right-click on the Start button (or WIN + X) and choose to shutdown via this menu instead.

See also: Shut Down Computer in Windows 10 - Windows 10 Forums

 

Hi there

I KNOW that insider builds are test builds but surely powering off and on a computer is the most basic operation there is -- how can Ms let this software out of the door with that defect in it -- don't they do ANY testing these days !!!!!

Cheers
jimbo

 

Does this happen with all copies or is it device specific? If it's all systems then I agree it should not be in the wild. But it's still better than Lotus sending out official cd's with a virus included for free *Wink ( the good old days of working on the wild frontier *Smile )

 

OK thanks Works fine

 

I can't tell if you're being sarcastic or not.

 

It is worse - they recognise this is an issue!

 

I really can't tell who's being serious and who isn't, but in the off case you are being serious, then you really need to change your understanding of how Windows 10 is developed.

MS release "snapshots" of the development process to insiders. These "snapshots" are in various stages of change, and as is often the case with change, some things may not be fully complete, or are even broken. MS isn't trying to get you to find these kinds of bugs, they already know they exist. They are looking for feedback on the direction of things, and they are looking to run this on millions of machines and receive the telemetry on them (something they could never do in their own environment).

As is always the case, if you aren't willing to deal with bugs, you shouldn't be in the insider program. Known bugs will always be released in insider builds, because.. guess what? It's not finished.

This is by no means a claim that the "finished" version is bug-free, but there is a huge difference between the "old" way of beta testing Windows and the new way...

Think about it like this. Suppose you are having a house built, or remodeled. At some point, the builder asks you to come take a look at the progress. However, when you arrive you find that the walls aren't even up! And there is only a flimsy door on this thing, that will never stop a burglar! They could just climb in through the spots where the windows are supposed to be! They must be incompetent right?

 

Mystere there a large difference between the severity of bugs. I agree with most of your post, however Microsoft should not let a build out of their doors which has a bug which means a hard shutdown is needed, not even on Insider builds.
That's the main reason I've gone over to Relese Preview builds for now.

 

A hard shutdown isn't needed. MS documented in the Known Issues that you could use the Alt-X menu to shutdown. There are also several other options to shutdown (such as the shutdown command prompt command).

 

For me that still isn't acceptable even for a Fast Ring build.

What next. An OS that won't boot due to a known bug *Biggrin

 

- Press physical Power Button (momentarily)
- Ctrl/Alt/Del - Shutdown
- WinKey+L - Power - Shutdown
- shutdown.exe
- SlidetoShutdown.exe
- objshell.ShutdownWindows
- WinX - Shutdown
- shutdown -s command prompt