Windows 10: Win 10 - Continuing Saga of Win 10 Unreliability

Hear ya. Did you shut off hibernation? Takes two seconds, command prompt(admin) powercfg -h off

When you get 10 back I would also run update trouble shooter. Obviously what you are seeing in not right.

Type troubleshooting in the Cortana search bar, troubleshooting appears at top. Click it, window opens, lower right side"Fix problems with Windows Update", click, window opens, click on “advance”, click on Run as administrator, click “Next”.
Should run clean. If not run again.

 

Again, it shouldn't have to be said, but Windows 10 is definitely ready for the prime time. If it had the issues you say, none of us would be able to run it properly, and I certainly wouldn't have it rolled out to 80 or so computers and counting.

Given your posts in this thread, you are clearly smart enough and have the understanding to know the issue lies elsewhere. Glad to see you address this the next paragraph. There's something unique to your system causing the issue, and the more time spent just assuming Windows 10 isn't finished is time not spent on the solution. Stress testing is an excellent idea.

I also think it is interesting that you can't repair the drive in this same computer. That alone tells me you have something going on with the configuration or stability. I have installed Windows 10 on dozens of various SSDs, from old Crucial C300s to brand new Samsungs in our Dell Latitudes.. Not one issue at all.

 

Maybe that is the problem, OP is too skilled, doing stuff most users would not even think about and that is breaking it. 10 is too sensitive, it has many dependencies, which might seem unrelated, but changing settings might break it.

 

Another voice with no suggestions is probably not needed, but that never stopped me before, so ...

I, too, am not a big fan of (my installations of) Win10 and have fairly regular hangups of one sort or another. But many Win10 users, including many on this forum, do not have my problems. Probably nobody has these problems. There is something in my hardware or software environment that Win10 does not like. Yes, it's frustrating. But Microsoft cannot possibly test Windows in every environment in the universe.

If none of the suggestions in this thread help you, perhaps you should report your problem to Microsoft. If you are very, very lucky they might find your problem.

More realistically, someone on this forum may help you identify the cause of your problem. But that is likely to happen only if you accept that it is Win10 in your environment, not Win10 in general, causing you grief.

 

Microsoft does try to test every system using Windows Error Reporting - part of the telemetry set-up of Windows 10. Whether they provide a solution depends on the statistical sample size, and common factors among the population of problem computers that can report their problems back.

Those in most need of a solution probably are the same paranoid users who try to turn off all aspects of their systems that report back to Microsoft!

If you get stopcodes (BSODs, RSODs, GSODs etc.), data from these will generally feed back into the WER system. If you get freezes, unwakeable sleep states and apparently random reboots, the user needs to escalate support by offering feedback themselves, else their problem will remain hidden.

Members with loads of experience on forums like TF, get to resolve many of these problems when the users cooperate with the requests for information, and with a genuine wish to resolve their particular situation by being open to try out suggestions, rather than just rubbishing the OS as the single cause of their trouble.

Those who just want to rant usually get there in the end due to the incredible zen of the members and gurus here who cannot let go of a problem until they have wrestled it into submission. It can take longer that way, but can also be quite entertaining, as the ranter is tamed into compliance, and the problem is exorcised with chants of "update your chipset and storage drivers" and the like.

I love the comment by @DeaconFrost "Stress testing is an excellent idea." - by which I assume that the acolyte is being kindly encouraged to take the path of ****x which will lead nowhere but eventually return back to the warm, safe, folds of Windows 10, chastened, but with a renewed joy at being back from the wilderness, where no business critical work is really being done, unless it is server-side, non-PC, or priestly work by the dedicated servants of GNU, Google and the like. There's nothing that cheers an old man up, as much as the return of a prodigal son.

 

I would like to add thoughts on your systems - Have you matched your ram & hard drive using the Manufactuers "QVL" list of tested working compatable parts as may a case of parts not guaranteed to work correctly ?

Also: In the user manual for your motherboard have you placed the ram into the correct slots as per manual & used identical make / model & size of ram ?

 

Well, Thank you all for some of the flattering comments like “smart enough and/or perhaps too skilled”. Let’s just say I’m not a dummy and a reasonably skilled, successful software engineer/developer, even simpler, a computer Programmer, a .Net Web Developer/DBA Programmer.

“Doing stuff most users would not even think about and that is breaking it. 10 is too sensitive” - Now that is Right on!, Exactly, How many people in this forum’s audience “MUST” have IIS, SqlServer, and multiple versions of Visual Studio and .net Frameworks on their daily workstation just to do their job? That is a well above average workstation requirement! In Corp IT, Systems and Pgming areas, a pretty strong, reliable, versatile box is definitely needed.

“it is interesting that you can't repair the drive in this same computer.” – Yea! That’s a Real Problem!
And my Biggest Single reason for saying Win 10 ain’t ready for prime time, and Busted!.
Backup and recovery was the first thing i tested with win 10. I’ve tested it a couple of times, and on different machines. I’ve never gotten it to work (and Win 7 does).
The very first time I installed Win 10, I installed the OS, set computer name, workgroup, made sure it connected, could see and was seen by the LAN, and installed Office. Next thing, Set up Backup and Restore, and did a create system image backup to the NAS - All completed successfully – OK( I liked it). So, I go a make a couple doc’s, test word & excel, played around and all ok. Then, next thing, I shutdown, dropped in the Win 10 CD, booted up from the cd, selected repair (rather than install), selected recover from sys image. All’s doin ok , it can’t find or see the network which isn’t unusual for some machines[didn’t wanta experiment tryin to load network drivers from CD repair recovery], so I just go to another machine and copy the good sys image from the NAS to an external 2T WD Passport, go back to the win 10 machine, plug in the Passport, try it again, it sees the local Passport, finds and starts up the recovery, runs about a minute and pops up an err msg, Recovery Failed, sometin like Invalid image for this system? What??? I just made this system image from this system! I’ve tried this on a couple Win 10 machines, even with an external plugged in locally when I made the backup recovery image – Never been successful, Hmm, OK, I’m either doing something wrong or Win 10’s Just Busted outa the box!
Have you or anyone here actually ever gotten this Backup and Recovery from system image to work? If so, Please sign me up for lessons and I’m buyin Lunch!
No Sys recovery is a show stopper for Win 10 in my department! Only Exec’s and Sales have Win 10 machines and/or Surfaces where I work…

This thread is getting too long, I’m gonna mark it as solved.
At this time, going entirely to Win 10 for IT, Sys & Pgming work requiring both System LifeCycle Maintenance and New Systems Development seams overly troublesome.
SaaS(Software as a Service) and Cloud Services are definitely in Vogue, Time will Tell.
I’ll get back in another thread, Later…

 

That is precisely what the Long Term Service Branch is designed for...

Overview of Windows as a service (Windows 10)

 

So there's your proof that there is an underlying issue with your system. You can't blame the manufacturer of a house if it was built on a poor foundation.

Except it is. Given what you have posted, you should easily be able to grasp this. We have no issues with it running in a very intense, highly-techcentrique environment. If it works for us, it surely isn't "busted".

 

Well, to be fair, just because Win10 is running in most environments doesn't imply there are no problems. There are a number of Win10 users that are experiencing problems. (I'm one of them.) Could be hardware. Could be bad drivers. Could be incompatible 3rd party software. Could be a lot of things. But the problems didn't show up until Win10, or Win10 AU, or some other significant Win10 change.

Does that mean Win10 is not ready for prime time? No - not if most users in most environments have no problems. It means more diagnosis is needed to uncover the problem. But problems experienced by a small number of people can be really hard to diagnose.

We with those problems need to be realistic. Telling Microsoft (or members of this forum) that "it's busted" isn't going to solve any problems. But man! it can be tough trying to describe apparently random, intermittent, inconsistent problems in any helpful way ... especially knowing that other people aren't having them. And it's easy to get frustrated knowing that we did not have these problems on Win7 (or Win8, or whatever).

 

No one is denying that it would be frustrating, or making the claim that it works perfectly on 100% of the systems it is installed on. It just defies logic and common sense to call the product broken or busted, unless pretty much everyone had an issue with it, and those issues are repeatable.

 

It will be interesting to see how that hardware works with a different OS installed. That would be the next logical step if you have convinced yourself that its the operating system that is at fault. And there is nothing wrong with the hardware.