B
BjornS1
Maybe it's me imagining, but doesn't the .Net Runtime optimization process run after each monthly windows update nowadays? I assumed that it only needed to be run after we had updates to the .Net framework and that is how I had found it to work in windows 2012 Server.
Anyone else that has the same feeling?
I guess the process is supposed to run at a fairly low priority, but it is definitely disturbing for an half an hour or so after the windows update has completed.
Continue reading...
Anyone else that has the same feeling?
I guess the process is supposed to run at a fairly low priority, but it is definitely disturbing for an half an hour or so after the windows update has completed.
Continue reading...