PDA

View Full Version : General Compiler error


K1LL3M
April 11th, 2009, 11:27 PM
Recently after turning computer on I have received this error, restart has failed to fix the issue.

I will try a reinstall to see if that solves teh problem, however I am curious how it could have occurred to begin with

DarrenDavisLeeSome
April 12th, 2009, 06:26 AM
Looks like you're running Vista.

Did you install the right bit version?

11/04/2009: Must not be the U.S. version. Europian? Australian? Vulcan? In the U.S. the format is Month/Day/Year...so...just asking.

Maybe the updates servers are running goofy?

Marcos
April 12th, 2009, 06:40 AM
Did you have beta or RC installed previously and installed the release version over it by chance?

littiman
April 12th, 2009, 12:48 PM
The same problem has happened in my brothers laptop as well. He has the 3.0.669.0 build and i tried updating today after 2 days from downloading the 3999 signature. The same error showed up. His system uses a windows xp professional sp3. What seems to be causing this? Anyone have any idea or solution to this unusual problem?

GaryRW
April 12th, 2009, 01:51 PM
I'm used to getting "Update Updater: compile error 0 NT AUTHORITY\SYSTEM" all the time. Haven't received any since v4000, but it may be for module updates only.

K1LL3M
April 12th, 2009, 08:25 PM
-{ Quote: "Looks like you're running Vista.

Did you install the right bit version?

11/04/2009: Must not be the U.S. version. Europian? Australian? Vulcan? In the U.S. the format is Month/Day/Year...so...just asking.

Maybe the updates servers are running goofy?" }-

Right Version V64 - Australian

-{ Quote: "Did you have beta or RC installed previously and installed the release version over it by chance?" }-

yes, I believe so, I don't think I did a clean install. But this has not presented itself before now and i have been using through all stages as soon as released. I will try a clean install and post back.


*Edit: I have done a clean install and this has resolved the issue currently, not entirely sure this was the problem as it had not presented itself till now, but it is working as expected and I can revive this thread if it re appears

Tx