• Welcome! The TrekBBS is the number one place to chat about Star Trek with like-minded fans.
    If you are not already a member then please register an account and join in the discussion!

Windows 10....one year later....disscussion, thoughts.

That is interesting. The only downside to the article is that it's from 2010. Windows 10 has set a new standard on data collection. Here's a more recent article (April of 2016) on what Windows 10 learns and what it keeps: http://www.chicagotribune.com/subur...about-windows-10-priv-1-2016-04-05-story.html

Also, concerns from Forbes about how invasive W10 can get: http://www.forbes.com/sites/gordonkelly/2016/01/06/windows-10-spying-secrets-revealed/#1221f3652fd5

Yeah, I just caught the date on that. thanks for posting more recent articles.
 
Yeah, I just caught the date on that. thanks for posting more recent articles.
You're welcome. It seems like Windows 10 is a mixed bag at this point. To be honest, I probably wouldn't have recommended it so heavily if I would have known the full extent of what Microsoft was going to consider acceptable practice. None of this was a major concern when Windows 10 was in beta, and so I was more willing to endorse it at that point. Between the final beta and the release, though, Jesus Christ they sure did amp up the volume.
 
You're welcome. It seems like Windows 10 is a mixed bag at this point. To be honest, I probably wouldn't have recommended it so heavily if I would have known the full extent of what Microsoft was going to consider acceptable practice. None of this was a major concern when Windows 10 was in beta, and so I was more willing to endorse it at that point. Between the final beta and the release, though, Jesus Christ they sure did amp up the volume.

Yea it's terrible. Thanks for sharing the links! What else don't you like about it so far?
 
I haven't had the problem ever since I did what you suggested. Thanks for the help. :)
You're welcome! :D

Yea it's terrible. Thanks for sharing the links! What else don't you like about it so far?
Not much else, really. Aside from what I mentioned, the OS is pretty solid and stable. They do need to work on Task Manager, though. There are some programs I run that even when you kill the process they don't go away. Windows has weakened that once very powerful asset somewhere. They need to put that back. Sometimes programs won't listen to "please quit" so you need Task Manager to kill it at the source.
 
I have had no real issues with it, does what it says on the tin, and i have that spybot anti-beacon thing that stops my paranoia going off the deep end. lol

But apart from that it all works fine and dandy.
 
You're welcome! :D


Not much else, really. Aside from what I mentioned, the OS is pretty solid and stable. They do need to work on Task Manager, though. There are some programs I run that even when you kill the process they don't go away. Windows has weakened that once very powerful asset somewhere. They need to put that back. Sometimes programs won't listen to "please quit" so you need Task Manager to kill it at the source.

Ah.

That sucks. What programs are running into that issue?

I agree. It comes in handy when programs sometimes freeze or run into other problems.
 
Not much else, really. Aside from what I mentioned, the OS is pretty solid and stable. They do need to work on Task Manager, though. There are some programs I run that even when you kill the process they don't go away. Windows has weakened that once very powerful asset somewhere. They need to put that back. Sometimes programs won't listen to "please quit" so you need Task Manager to kill it at the source.
What about killing a process from the command line. Is it just as ineffective?
 
Ah.

That sucks. What programs are running into that issue?

I agree. It comes in handy when programs sometimes freeze or run into other problems.
The one that caused the most problems was Battlefield: 1942, which ran perfectly fine on Windows 7, and did work fine on Windows 10 until the last update. I would try to kill the process from TaskMan and it simply ignored it entirely, and would freeze up TaskMan, which shouldn't ever happen.

What about killing a process from the command line. Is it just as ineffective?
I haven't tried it from the command line, so I'm not sure.
 
The one that caused the most problems was Battlefield: 1942, which ran perfectly fine on Windows 7, and did work fine on Windows 10 until the last update. I would try to kill the process from TaskMan and it simply ignored it entirely, and would freeze up TaskMan, which shouldn't ever happen.


I haven't tried it from the command line, so I'm not sure.

Dang. That's not good.

How do you kill a process in Command Prompt? Never had to do that before.
 
Dang. That's not good.

How do you kill a process in Command Prompt? Never had to do that before.
It's pretty easy, though I don't ever really do it because TaskMan usually takes care of it. Here's the whole process: https://technet.microsoft.com/en-us/library/bb491009.aspx?f=255&MSPPError=-2147217396

The long and short of it is you just run taskkill [parameters] and then it kills the process. I may try to run Battlefield:1942 again just to see if I that will work. What I do for you people in the name of knowledge! ;)
 
It's pretty easy, though I don't ever really do it because TaskMan usually takes care of it. Here's the whole process: https://technet.microsoft.com/en-us/library/bb491009.aspx?f=255&MSPPError=-2147217396

The long and short of it is you just run taskkill [parameters] and then it kills the process. I may try to run Battlefield:1942 again just to see if I that will work. What I do for you people in the name of knowledge! ;)

Ah so basically you input the names of the processes you want to kill such as ituneshelper.exe as a part of the command itself?

Found an easier way... tested it out on Notepad via its PID and it works, via CMD. Woot.
 
Last edited:
CSyo3khWIAAREfJ.jpg
 
New build has come through for the fast track insiders. Will shortly see what they've managed to screw up this time,
 
I'm glad I stuck to Win 8.1, rule of thumb usually is that M$ will take at least 2-3 years to make an OS usable...
 
Welp, I got the dreaded un-exitable popup today. Didn't have much of a reason not to upgrade other than having an older computer, so I'm waiting for it to install now...... We'll see what happens.
 
Windows 10 was great to use right out of the gate, now Windows 8? That was a clusterfuck.
Indeed. I still stand by my initial statement that Windows 10 is a solid OS. It needs some work, and I really wish they would tone it back on the privacy issues, as not everything needs to be integrated into everything else, but otherwise this is the most stable, most flexible, easily the most cross compatible OS that Microsoft has released since Windows XP SP2.
 
Indeed. I still stand by my initial statement that Windows 10 is a solid OS. It needs some work, and I really wish they would tone it back on the privacy issues, as not everything needs to be integrated into everything else, but otherwise this is the most stable, most flexible, easily the most cross compatible OS that Microsoft has released since Windows XP SP2.

agreed - for home users and those who don't get the insider track upgrades it's been very stable. Neither my mum or mother-in-law have had any problems.

I think it's business users and perhaps the more technically minder who are a little peeved with certain elements that Microsoft should have sorted out before the release.
 
Ugh so many forced reboots through the power button of this POS. The Windows ID login can stall for ages and shutting down will happily lock up too unless manually done.

It freezes when certain tasks are running, like absolutely freezes, haven't had a computer do that in a long time, etc

Damn OS just likes to lock up entirely at random. Vista wasn't doing this kind of thing, not that frequently anyway.
 
If you are not already a member then please register an account and join in the discussion!

Sign up / Register


Back
Top