disabling of hardware virtualisation didn't help, deleting avast since spam these messages in even log. I am not planing any action on my windows 7x64 setup for now, i have tried to install many AV's since i install the system in early august 2014, like quihoo 360 total security, previous versions of avast and many other software freeware or open source. Since i have many errors and delete old august system restore snapshots i only apply whole windows updates with microsoft tools, doing sfc /scannow + chkdsk with force keys and so on. Some errors might be continue to show up in event viewer, but i don't mind em and personally i don't care, since i can't get to work oracle virtual box vm software on my old Q9300 CPU even with enabled virtualisation in BIOS, i use vmware instead for now and it's simply works. If newest version of avast using some mechanisms from virtual box (vbox is showing me some sort of DCOM errors when i install it even on fresh windows 7 x64 ultimate with OEM license) I personally wan't option to shut down these completely with sandbox for me, cause if i disable these features in avast now, they continue work on my system and spamming whole event logs with avast COM errors. Even if my system has long term issues with software installation/uninstallation then continued troubles with DCOM/COM applications and so on i have to be able to run your antivirus without any issues.
Microsoft states one last position about my problem to using windows restore option or recover OS installing over old one, that I won't to do now, cause it's gaming PC and I have a GRUB installed in my system hdd boot sector, so if I launch restore this way, these might be interfere with my GRUB(ubuntu 14.04 LTS installation) on my system hdd. You clearly understand that i won't restore windows, then restore GRUB and order of loading my dual booting configuration. Even though i have no specific issues with DCOM/COM services for now, all services.msc is running as intended and i have almost clear even log without any errors. These system i mean windows installation is three month old, and virtual box won't work either when i install it in early august showing me some weird errors about "can't create some active COM object". I've tried to google these thing, but haven't found virtually nothing new about these error, only old 2012-2013 year messages and it is stalled solved bug. I've changed my processor in early august, previously I using Q9450 but then I crack it when trying to remove termal interface metal cover, so these issues with virtual box is showed up when i install new Q9300 processor in the same configuration PC. I've tried to do some registry fixes applied to vbox installation in some keys that have linked up with vbox install path directory to x86/x86-64 libraries but still haven't succeed to run vbox properly on these fresh OEM Q9300 CPU...(and these CPU is fully compatible with NX bit + virtualisation which is enabled in my BIOS
then I just setup vmware workstation and it works perfect for me...).
:-\well what I am trying to say, that I really don't know why new oracle virtualbox and avast sandbox implementation doesn't like my CPU and why is this happens to me...if someone can put some light on these issue I appreciate any kind of help and support ><...but for now i have to simple remove vbox and avast from my PC to do not fill event log with bunch of errors, sadly but true....
P.S.> & sorry for my bad english, I am leaving in Russia