hi guys,
anyone have a machine with the new v4 chips yet?
We are having a problem with not being able to set cpu affinity in task manager, and also various other windows 10 problems such as a weird thing called runtimebroker.exe using 100% of one core, all the time.
any help much appreciated
Peter
interrested in some feedback as well as i was planning to get a dual xeon v4 WS… 
I have also meet the runtime broker gremlin. It’s a Windows 10 program that manages Windows 10 apps. I kill it 3-4 times a day.
Do you have UAC turned on or off? I turned it off on my Windows 10 at home. The steps to do this are somewhat more convoluted now and there is no UI for it, I had to change some registry setting.
Best regards,
Vlado
Among the more useful proposed solutions for me, stopping runtime broker, was to turn off “Show me tips about Windows” in Settings:
Open Settings (Press WIN+I)
Click System
Click Notifications and actions
Turn off Show me tips about Windows
Also of note is checking whether network locations have been added to a library, and that they haven’t been indexed.
I have tried this, but it didn’t solve my issue.
And checked you mapped network locations and library folders? Windows indexing can have a large overhead…
Everything I have is local. I don’t want to hyjack, it’s just I have been trouble shooting this for over a month. I did just turn off my UAC, which was offered when I went to install something. I’ll report back.
Bobby I only iterate on the indexing thing as you might have drives attached for your backups. Have had this happen in other companies, and letting indexing complete has mostly solved the issues. Wasn’t brilliant in Windows 8.1 and from what I’ve experienced is worse in Win 10. Try keeping things unplugged and message back with how it goes.
Peter, hoping not to sound too simple, but to save time can you confirm you’ve followed the points in this thread:
Will do. I do have a couple backup drives.[quote=“t.petrov, post:9, topic:48442, username:t.petrov”]
Bobby I only iterate on the indexing thing as you might have drives attached for your backups. Have had this happen in other companies, and letting indexing complete has mostly solved the issues. Wasn’t brilliant in Windows 8.1 and from what I’ve experienced is worse in Win 10. Try keeping things unplugged and message back with how it goes.
[/quote]
yep, it just wont let us past step 6 !
tried all this, and even tried uninstalling all windows 10 ‘metro’ apps. No dice.
We have 7 or 8 machines all running windows 10, the only ones with the annoying runtimebroker issue are the brand new ones with the xeon v4 cpus.
as far as I know UAC is turned off, I just dragged the slider to the bottom, but perhaps that doesnt completely turn it off??
Don’t know about the UAC or runtimebroker, but I do know that I turned off most of the windows 10 clutter with a few of these: Windows 10 Privacy tool: Comparison of antispy tools - gHacks Tech News
uninstalled all windows 10 ‘metro’ apps, still got the runtimebroker issue. ONLY happens on the machines in the office with more than 64 cores. I reckon it is a windows 10 issue that needs to be fixed. Hopefully once more people get these machines microsoft will fix it.
Hi everyone,
im also expecting cpu’s (2x40 = 80cores) to arrive during this week, and i just saw a problem here with vray and not detecting the total amount of cpus,
friend of mine already got them and he has the same problem with vray, thing is he tested corona, and everything is working great, so Peter my advice to you to try corona and see is everything working as it should…
corona test
vray test
according to this i think the problem is with vray, sorry vlado
waiting for updates…
p.s.
before these 2x40 cores, friend had 2x28cores and vray was using all cpu’s so i guess there is a limit to lets say 64cores or something like that, perhaps?
cheers
Ok Bazuka, a shame you haven’t read this thread though - the experiences here are far more to do with Windows 10, rather than vray, not behaving with large core count xeon… Also vray has supported greater than 64 cores for a while now (previously with an environment variable, and since 3.3 by default).
Sorry, Bazuka, there’s no problem with V-Ray. For the 3.30 builds, you need to enable support for more than 64 cores for V-Ray by setting the environment variable VRAY_USE_THREAD_AFFINITY to 1. This is enabled by default for later builds.
Best regards,
Vlado
Hi vlado, he did enable the env var, and still not working,
but we found out whats the probl, according to windows, i think u should better read this, you will understand, but ill try to explain to other people with simple words whats going on 
so someone from Microsoft made that if u have (computer with) more than 64cores, windows will make a 2 groups! (dont know who was that smart to make this so stupid, no case in linux)
group1 (with max 64cores) and group2 (other max 64cores group), so people like a friend of mine with 80cores has also 2 groups of cpu’s, divided by 40cores in each group (since they are physical cores) and as i explained vray see only that one group of the 2 groups…(that is 40cores)
soooo, the only solution is to, i dont know, rewrite vray or something so it could read both of the groups, thing is software should be written to read groups, (looks like guys from corona did that, or what ever), just to make it clear here, im not saying that corona is better, thing is we tried with houdini 15 and had the same problem, h15 see only one group ->40cores…
article about houdini problem
but as far as i see even in Peter case still not working, right? with that env variable?