Windows 10 [2014 - 2017]

Talking of virtual machines, this is me today running 4 virtual PCs with 4 different OSes (Windows 95, Windows XP, Windows 7 and Windows 8.1 --which I love to death, never understood the hatred towards W8) on a single OS, Windows 10

 

you need to run BeOs now

 

I wouldn't mind to. https://winworldpc.com/library has a BeOs version, although I don't know how to install it. Another is Yosemite -quite difficult, I guess, 'cos of the closed hardware of Apple, but I am gonna make it-, Android -under Linux stuff, might not be not so straightforward on Virtual Box-, debian, Ubuntu and so on and so forth

 

What... It won't be legal even when force activated using kms

 

Yeah I don't understand. How could your mind even conceive of that bring remotely legal.

 

All the (physical) boxes in my house are now Win10, save for my home server which is Server 2012. I'm at least mildly curious what will happen when I eventually upgrade my gaming rig with a new mobo, but that's probably another year or two away at the least. By then, we'll all be bitching about WinRedStone version Eleventy...

 

Anyone else have a problem with this update repeat installing/failing?

Its been apparently trying to install since 14th Jan, recording as 'successful' rather than failed each time, is kinda weird.

Edit: or I could google...
https://support.microsoft.com/en-us/kb/3119142
They know about it & supposedly can be fixed by running Repair on the appropriate installation.

 

Had the same issue again, none of these worked.

But the window still open, .exe still showing in Task Manager

Same running as Admin.

 

@hoom
you need to use Process Hacker, then use "terminator".

but if the program is too stubboron to kill... you may get a risk of total system lockup

 

This never happened with Win7.
I mean, the game would stop responding but Task Manager Kill always worked. Always.

There is something pretty fucked up if you need to run some 3rd party app in order to kill a task because the OS won't let you.

 

Unkillable processes have happened to me since at least winxp. Hasn't happened to me yet in win10, though, so it's a bummer to hear it's not immune.

 

Personally I'd try "Resource Monitor" before going to a 3rd party app. This allows you to track individually processes and kill them and their entire tree. Task manager tends to show some abbreviated processes data and often won't show you exactly what background processes you know are running because your laptop fans are wailing away while resource monitor is much more detailed.

 

You mentioned that running the taskkill command on the second time results in a message that Rome2 task isn't running. Are you sure it's not some "wrapper" process still leaving a window behind?

I did a bit of Google for killing off Rome2.exe; it's not really showing up as much as I would expect for a "common" problem. There was a hotfix for WIn7 / Win8 / equivalent Server products which patched Taskkill to solve problems where it couldn't kill a process and would tell you the process didn't exist. This doesn't appear to persist into Windows 10...

 

Process Explorer from Sysinternals is a tool you might install without much of a second thought : it has long been acquired by Microsoft, who in particular wanted to hire his well-known author Mark Russinovich (it was said that he knows more about those dirty under-the-hood things than Microsoft engineers do). So it's something of a 1st-party add-on.

About taskkill I believe it doesn't do anything different than clicking in the task manager.

 

I think process Explorer also have terminator

 

One cause of "un-killable" processes that I've run into is if the storage device of the program becomes inaccessible for some reason, then Windows sometimes will not be able to kill a task that is stored on that device. I recently ran into this while helping a friend with a similar problem. He had an SSD drive that would intermittently become inaccessible in Windows and whenever that happened a couple of the programs he ran on that drive would become un-killable. It would also cause Windows Explorer to hang if you attempted to access the drive while this was happening until you either powered off the drive somehow, or the drive became accessible again. Once you did either of those things, Windows would then be able to kill the task.

Was a very strange problem that I hadn't run into prior to that.

Regards,
SB

 

Sometimes the command attrib in cmd might be helpful, but I don't know. By the way, on a different note, now Edge supports WhatsApp web. I don't know why people prefer WhatsApp when there is Telegram, but anyways..

 

Now Windows 10 shares your VRAM with the RAM.



Btw, I have a new web browser, called Maxthon, and I find it awesome, original and different. It comes with Adblock enabled, it has a proxy and so on. Chinese are brilliant in cases like this, got tired of the clone browsers we have now, Chrome, Opera, Firefox, etc. If you don't have admin rights in your main account download the portable version of Maxthon

 

I thought even Windows 7 shared main RAM with VRAM, or is it just actually good at it now?

 

Isn't Maxthon just a wrapper over IE?