Problems with windows server 2008 r2 updates

[silvered.dragon]

Dear friends this is my first post so I hope that you will help me to figure out,
I have two equal configurations on 2 differents IBM servers with same issue: during the first heavy updates the guest os is searching for updates for hours until the virtual machine will abort and I have to reboot the machine with same issues.. everything else is working fine, can't undestand why this is happening but I have the same situation with windows xp updates on another istance. All my iso are untouched and this is my configuration

server is IBM X3650 2 x quad core XEON 5460
OS host is debian 7 fully updated(server version only CLI)
OS guest is windows server 2008 r2 64bit
Virtual Box is 4.3.20 in a compleaty headless environment
all extension pack and guest addiction are updated to last versions

SOME PARAMETERS
memory 2048
accelleration VT-x/AMD-v, Nested Paging,PAE/NX
IO/APIC enabled chipset PIIX3
processor allocated 2
display 16MB
storage dinamically allocated 200GB
NETWORK IS BRIDGED WITH PROMISCOUS MODE ALLOW ALL
AUDIO/USB DISABLED

I think that this is reletaed with memory issue but not sure.. maybe I have to allocate 4GB cause this is a 64bit OS?
thank you!

[socratis]

Unfortunately, you don't provide any detailed information (like the zipped VBox.log, you should definitely do that by the way), but here is a suggestion. Take a look at your guest's power-management options and screensavers and if they are enabled, disable them.

[silvered.dragon]

thank you mister and sorry for my poor information but i figured out from this.. googleing all the night I found that it was a common problem with microsoft OS that may happen on vbox installations, to solve this just install this usefull fix selecting the right operating system( I can't past links so simply search on google for KB947821 and select right operating system version) and worked for me perfectly! thank you again

[socratis]

Thank you for pointing to the KB947821: "Fix Windows corruption errors by using the DISM or System Update Readiness tool". I'll briefly mention the symptoms so that the search engines can help someone in the future. From the article:

Windows corruption errors prevent Windows updates and service packs from installing. For example, an update might not install if a system file is damaged. If the error you see is in the following list, try the solution in this article.

0x80070002 | 0x8007000D | 0x800F081F | 0x80073712 | 0x800736CC | 0x800705B9 | 0x80070246 | 0x8007370D | 0x8007370B | 0x8007370A | 0x80070057 | 0x800B0100 | 0x80092003 | 0x800B0101 | 0x8007371B | 0x80070490