• Security incident: ISF was recently accessed by intruders. Please change your password, and change it anywhere else you used it. Read more

Poll: Are you happy with Windows 10?

Are you happy with Windows 10?

  • Yes, no problem with installation or using.

    Votes: 80 42.6%
  • Yes, after some initial problems installing or learning.

    Votes: 30 16.0%
  • No, not happy at all, will uninstall.

    Votes: 4 2.1%
  • No, not happy at all, can't uninstall.

    Votes: 5 2.7%
  • "Happy" would be a stretch.

    Votes: 13 6.9%
  • Too fancy for me, but I gotta use it for work.

    Votes: 0 0.0%
  • Still waiting to see if I'm going to do it.

    Votes: 16 8.5%
  • Never going to upgrade.

    Votes: 9 4.8%
  • Not going to upgrade until I'm forced or I buy a new computer.

    Votes: 26 13.8%
  • Planet X has been declared a dwarf planet. Chose this option if you're 3 feet tall or less.

    Votes: 5 2.7%

  • Total voters
    188
I was happy with Win10, then incredibly unhappy, now reasonably content. I won't be going back to an earlier OS. Here is what temporarily did me in, and had me in fits: I decided to reinstall Win10 natively and rid myself of legacy items (just take a look at the reams of outdated junk in the Task Scheduler library on an updated Win7 or 8 system, some of which gave me issues).

All proceeded well, until I decided to install a major media suite to have better access to 3D videos on the PC. Long story short: if anything creates a hiccup with the new GDI scaling, such as an application that does not 'understand' G-Sync variable refresh-rate monitors, you are in for major misery. In the case of that application, it could not read my media files or libraries at all, and would hang miserably. The fix was to use a fixed refresh rate, but that negated an important functionality.

I got to the point, prior to solving that issue, of tearing my hair out from resolving every single flagged error in Event Viewer. Yeah, I know, EV can be grossly misleading, but in the absence of any other tracking mechanisms, it is all one gets in Windows, and so one is reduced to solving things that are transient only, need no solving, or which break from "fixing." I do now have a nice set of important fixes worked out, nevertheless.

Here is a curious combo: If I leave my Samsung phone plugged into a USB port upon booting the PC, most of the time the driver fails, which in turn somehow affects my fix for the font security failures in the OS (namely, allowing the service to get through the local firewall), which then means GDI fails, and a frozen desktop results. Boot without the phone plugged in, and all is dandy.

To end, I'll just say the experience so far has taught me Win10 still has some major bugs under the hood, but so does every earlier platform. I'm reasonably happy, although I'd take the full screen application menu of Win8.1 over this weird useless thingy any day. Classic Shell, which I stopped using under 8.1, is back on my system. Sigh.
 
Here is a curious combo: If I leave my Samsung phone plugged into a USB port upon booting the PC, most of the time the driver fails, which in turn somehow affects my fix for the font security failures in the OS (namely, allowing the service to get through the local firewall), which then means GDI fails, and a frozen desktop results. Boot without the phone plugged in, and all is dandy.

To end, I'll just say the experience so far has taught me Win10 still has some major bugs under the hood, but so does every earlier platform. I'm reasonably happy, although I'd take the full screen application menu of Win8.1 over this weird useless thingy any day. Classic Shell, which I stopped using under 8.1, is back on my system. Sigh.

thanks- my new laptop was hanging for no apparent reason- unplugged the samsung and bingo- it booted fine!

had no custom drivers, but it does have a older networked tv tuner- unplugging it also results in no crashed startups- so its probably a video driver thats causing the issue imho

unfortunately the logfile doesnt show any crashes/ stoppages- so in that its pretty useless
 
OK, today I am back at detesting Win10. Here's why: they broke sharing and networking with something called SMB 2 & 3. I'm just getting started on my reading, so don't ask.* It seems that if you also sign in with a Microsoft account, as I did until today, networking setup sort of expects to be in a domain all the time and tightens security setting that make homegroups and accessing a NAS nigh impossible.

I'm sure I'll find a fix, but this is what, a month of on/off debugging sessions that last several days each? I haven't had to "support" an OS this much since I was installing Win98SE on machines with large disks and lots of memory. If it stays this broken, I may go back to 8.1 and start really hammering MS in support sessions as a paid user, with no future, asking for a new solution (bag Win10, it is hopelessly borked).

I mean, the start menu is two broken systems gerry-rigged together, with the obvious solution of allowing either style, Metro or menu, full-blown, still beyond Redmond's wildest inkling. Then there are all the folders, registry keys, and DCOMs with erroneous permissions out of the bag. Wouldn't be so bad if these errors did not end up borking Apps and the Store all the time. But then comes the real whammy at the end: the PowerShell fix that corrects App installations is so broken in this release that if you run it, the whole shebang gets wiped.... Eegads! And then there's the font scaling tech needed for cross-device apps: also prone to breaking, or having a flu on boot.

So, the brave new device-independent App world that MS has made the cornerstone of its future is exactly what most sucks about Wiindows10, from the menu, to the background device technologies, and on to the dedicated maintenance scripts. This does not bode well.

---
* Cannot connect to my NAS since Win7, didn't bother to try under short-lived 8.1, and now can't use it at all under 10. Also cannot see my living room PC from this one and vice versa, be it networking or homegroup.
 
I haven't had any problem but I have always set up my file servers to require authentication for SMB (SAMBA).

From what I've read Microsoft tightened up network security in the Win 10 SMB implementation. If you have a NAS setup that uses guest mode instead of authentication then you can either setup authentication for SAMBA on the NAS or disable the Win 10 security requirement with a manual registry edit.

For the most simplified details I've seen for the registry edit read this: https://www.schkerke.com/wps/2015/06/windows-10-unable-to-connect-to-samba-shares/
 
Broke down about three weeks ago and installed Win10; had to have it removed and Win8 reinstalled by Dell support.

10 would not start/restart the laptop. Spent a frustrating week on the phone with Bangalore trying to suss out and repair the problem - they finally sent a USB with Win8, reloaded it, and I'm back to computing again!
 
A few years ago (4, to be precise) I did some consulting. One of the things i got was Autodesk Mechanical and Inventor Fusion.

Windows 10 cost me that program--Autodesk has no intention of supporting anything more than 2 years old, and Win 10 flat-out will not let the Fusion part run. I got the mechanical up and running, but I haven't tried to wring it out--and i won't
Now, Physics have not changed a whole lot in the ensuing years, and the FEM capability I got at $8000 (US) was/is very good and powerful. When the contract finally ran its course, I had done reasonably well, and had future capability. Just not with Win 10.
So i reverted to Win 7
It appears to be a .Net 4.6 issue. Looks like I will be maintaining a Windows 7 machine for a long time--just gotta make sure to stay away from .Net4.6
 
Does Autodesk run in a VM?
Quite frankly, I don't know. I would like to find out, but even with the original installation disks, I cannot get any virtual machine to actually load an OS in Windows 7. It keeps blowing up over a missing dll or something
( I have not tried to load Linux and a windows emulator, because I don't have a clue )
 
There's a fair few complaints that Win10 is installing "without permission"

The Guardian report

In our case we get pretty aggressive reminders on our Win7 desktop (Install now/later/choose time) but the 8.1 laptop stays quiet on the subject.
 
The Get Windows 10 program was activated on PCs on an Active Directory Domain with Professional versions of Windows and lower recently. I tried to use the manual techniques for eliminating it on two engineering workstations last week. There were so many steps and re-boots required I finally gave up and just used the GWX Control Panel to get rid of it.

Fortunately for IT, we are in the midst of upgrading everyone else to 10 so it's only a few PCs that need to be kept back on Win 7.
 
hahahaha your last option had me rolling on the floor. The thing is, is I feel that windows 7 is where it's at. windows 8 was a horror story and windows 10 wasn't any better. I will say that if my computer was touch screen my opinion would change.
 
hahahaha your last option had me rolling on the floor. The thing is, is I feel that windows 7 is where it's at. windows 8 was a horror story and windows 10 wasn't any better. I will say that if my computer was touch screen my opinion would change.

I'm seeing a lot of complaints about "One or more network protocols is missing." That's what drove me back to 7 and I'll be staying here up criticality is reached in the OS dept.
 
Well, I guess I add myself to the no problems list, as I just got a new laptop with Win 10 preinstalled, and it seems to be working fine. I hated to do it but tax time is coming around and Turbo Tax won't run on XP any more, and I'm not ready to ditch the big old XP desktop which runs some legacy machines and works very well, so I bought a cheap Dell laptop from Staples, and it's not bad at all. It certainly seems to run faster, and crashes less on the net than my previous Vista laptop. Of course Vista....that one was a freebie and looks as if as soon as the data come off, it's outta here.
 
I'm seeing a lot of complaints about "One or more network protocols is missing." That's what drove me back to 7 and I'll be staying here up criticality is reached in the OS dept.

That is a really annoying bug, and there's no excuse for Microsoft not having fixed it months ago.
 
I'm seeing a lot of complaints about "One or more network protocols is missing." That's what drove me back to 7 and I'll be staying here up criticality is reached in the OS dept.

Had that, the problem seemed to be Windows Update, and solved by running the Windows Update diagnostic.

The real fun with Windows 10 was getting a NAS backup drive working; a series of random and rare Windows errors with no rhyme or reason.
 

ISF - Join now!

Every member here is approved by hand. No bots, no spam, just people who care about evidence and honest debate.

Membership is free!

Create your free account

Back
Top Bottom