EEK! emergency max wierdness

[super gnu]

Im going away this weekend for a break. but i need to do a ton of rendering over the weekend while im away. max/vray/backburner have been working perfectly since i built my pc.

in the past few days ive installed vray5 beta (for the Light path expressions)

yesterday i also ran windows update, to get it out of the way (its been asking me for ages, and i didnt want to risk it updating over the weekend)

after these two changes everything carried on working as normal.


yesterday, to get ahead, i queued up a load of sequences on backburner.

they started rendering fine, so i let it going and went to bed.


this morning, half the sequences are finished, the rest are flagged with errors.

if i restart any of them, i get an IMMEDIATE error about 3dsmax being unable to start.


if i start 3dsmax manually, i get a message "do you want to allow 3dsmax.exe to make changes to your computer?"

ive literally never seen this message before for 3dsmax. why is it asking now.?

i turned off UAC on my pc to remove the message.. this worked for starting max manually, but backburner still errors out if i try to run a network job.


i dont think its vray related, max doesnt even try to start.


wierd thing is, first few sequences rendered fine last night, next sequences actually did a few did a few frames each... so its not even a sudden, total failure...


if i cant fix this quickly i wont be going on holiday and ill probably get a divorce... so.. any suggetions appreciated


EDIT: ive tried rolling back the windows updates.. no change.

EDIT2: tried uninstalling vray.. no change.

[super gnu]

OK so a system restore fixed the max error

but then my rendering was failing again every few frames

it appears to be the bucket issue of vray 5 beta which was flagged elsewhere

my only vague theory, is that max threw so many errors during the night, that windows somehow flagged max as a "problem" and added this "do you want to allow" message to max, which broke backburner


dont even know if windows 10 does that kinda thing


wouldnt surprise me


anyway im testing the latest nightly for the beta, which seems to be working fine


if it remains stable till tomorrow ill stick with it

otherwise back to next!