I accidentally set all of my stuff to the same affinity

[agma77]

I accidentally set all of my stuff to the same affinity. How do i revet these changes? everything is set to 0-15. I was just trying to disable hyper threading and then revert it. I also activated pro balance on them.. I was trying to fix things and I think I am making things worse. I also set one to none because I was trying to figure out how to fix the issue.

[Jeremy Collake]

Use menu item "Options > Reset Configuration", then restart your PC. No changes will have persisted.

[agma77]

What if that doesn't work? It's still doing the same thing. scvh host says the cpu set is 0/0-15 also. a lot of the rules have n x on them but when i check their rules it shows nothing.i just did a system restore for a few days back and it didnt help.i even hard reset my computer and it didnt work. now steam cant even access my d drive. how do you reenable hyper threading?

[Jeremy Collake]

The "X" (excluded from ProBalance) will be seen on hard-coded exclusions. It's a signal to do nothing to that process.

Some processes, such as svchost.exe instances, will have CPU Sets that they themselves set. Process Lasso is reflecting that.

There's nothing left that Process Lasso is doing, so I think you'll eventually discover the issues you're having are elsewhere. However, to confirm that, you can uninstall Process Lasso for an extended period, say a few days.

Hope this helps!

[agma77]

i havent fully tested out my pc after this issue came up. so I caned set the cores back to the way they used to be? someone else said i need to individually change them but I have no idea what I would change them to. does lasso automatically use all my cores and all that? I looked and it says mine i9 has 16 cores and the options lasso is giving me is 0-15 cores. I figured out the D drive issue. if all my stuffs at 0-15 is that an issue?

[agma77]

The "X" (excluded from ProBalance) will be seen on hard-coded exclusions. It's a signal to do nothing to that process.

Some processes, such as svchost.exe instances, will have CPU Sets that they themselves set. Process Lasso is reflecting that.

There's nothing left that Process Lasso is doing, so I think you'll eventually discover the issues you're having are elsewhere. However, to confirm that, you can uninstall Process Lasso for an extended period, say a few days.

Hope this helps!

I really just want to reset my stuff back to normal but it doesnt seem like there is a way to do it. so now I have to manually assign these things to cores? if i just uninstall lasso does this all go away?