Doesn't run on Windows 7

[Daniel Might]

When I try to start the game, it doesn't run. Neither from the Steam shortcut, nor directly from the exe. I'm running Windows 7 Ultimate 32 bit. Funny thing is, GTA3 runs fine. Updating the video drivers is not an option for me so I'm hoping something else could be the problem.

[XXIV]

try to run in compability mode, windows xp server pack 2 should work. To do that, go to Steam/SteamApps/Common/GTA Vice City, and go to properties in the .exe file. Run on Admin too.

If it doesn't work try to re-install. Running fine here. (windows 8.1 Enterprise 64 bits, I didn't have to change nothing)

[Daniel Might]

Thanks for the response. I tried that, but it didn't do anything. When I start the exe, it asks "do you want to allow this unknown program to make changes to the computer" and when I click yes, nothing happens.

[XXIV]

Originally posted by Raynaldo:

Thanks for the response. I tried that, but it didn't do anything. When I start the exe, it asks "do you want to allow this unknown program to make changes to the computer" and when I click yes, nothing happens.

That's really strange.

Try to search on google, maybe something will turn up.

If you can't find a solution, then try to re install the game. If that doesn't work too... Well, contact the Steam Support, maybe they can help you, or at least give you back the money.

[Joker]

Disable Windows UAC and add gtavc.exe to Windows DEP exceptions list.

[Daniel Might]

Originally posted by ΘPG| JCAP:

If you can't find a solution, then try to re install the game. If that doesn't work too... Well, contact the Steam Support, maybe they can help you, or at least give you back the money.

Thanks OPG, I tried reinstalling, didn't help. I don't need money back, I bought the whole GTA collection and I've managed to play when I had XP. If I contact support, they would tell me to update the graphics driver which would probably solve the issue, but I'm looking for another way around because I have an old card (gf6600) and new drivers actually cause more problems than they solve for me.

Originally posted by lo0n:

Disable Windows UAC and add gtavc.exe to Windows DEP exceptions list.

I have no idea what you just said, pal xDD

[Shadowman]

i have same problem with win 7 but it says out of memory but i have 16 mb and grafic card is gtx 660 so i think that at game is to old. the new uppdate of steam then it works fine

[Joker]

start
control panel
action center
change user account control settings

turn the slider down to "never notify".

then back to control panel

system
advanced system settings
performance/settings tab
data execution prevention tab

check "turn on DEP for all programs and services except those I select"
click "add"

go to

C:
Programs (x86)
Steam
SteamApps
Common

Go to the Grand Theft Auto Vice City folder and select gtavc.exe to add it to the DEP exceptions list. It would also help to right click the gtavc.exe, go to the compatibility tab and select run Windows 98/Me & run as admin.

[.]

I usually just close everything other than steam and gta vc and that usually works

[802Trip]

get a better system, 32bit prossecors are slowing fadeing, i would reccomend getting a better system (64-bit proccesor)

[Daniel Might]

My processor actually IS 64 bit, but it's extremely old so using a 64 bit system does more harm than good.

[GalacticPond]

This is what an unhandled exception is=

Microsoft "This event provides notification of uncaught exceptions. It allows the application to log information about the exception before the system default handler reports the exception to the user and terminates the application. If sufficient information about the state of the application is available, other actions may be undertaken — such as saving program data for later recovery. Caution is advised, because program data can become corrupted when exceptions are not handled.



NoteNote


In the .NET Framework versions 1.0 and 1.1, application termination and debugging options are reported to the user before this event is raised, rather than after.


This event can be handled in any application domain. However, the event is not necessarily raised in the application domain where the exception occurred. An exception is unhandled only if the entire stack for the thread has been unwound without finding an applicable exception handler, so the first place the event can be raised is in the application domain where the thread originated.



NoteNote


In the .NET Framework versions 1.0 and 1.1, this event occurs only for the default application domain that is created by the system when an application is started. If an application creates additional application domains, specifying a delegate for this event in those applications domains has no effect.


If the UnhandledException event is handled in the default application domain, it is raised there for any unhandled exception in any thread, no matter what application domain the thread started in. If the thread started in an application domain that has an event handler for UnhandledException, the event is raised in that application domain. If that application domain is not the default application domain, and there is also an event handler in the default application domain, the event is raised in both application domains.

For example, suppose a thread starts in application domain "AD1", calls a method in application domain "AD2", and from there calls a method in application domain "AD3", where it throws an exception. The first application domain in which the UnhandledException event can be raised is "AD1". If that application domain is not the default application domain, the event can also be raised in the default application domain.



NoteNote


The common language runtime suspends thread aborts while event handlers for the UnhandledException event are executing.


If the event handler has a ReliabilityContractAttribute attribute with the appropriate flags, the event handler is treated as a constrained execution region.

Starting with the .NET Framework 4, this event is not raised for exceptions that corrupt the state of the process, such as stack overflows or access violations, unless the event handler is security-critical and has the HandleProcessCorruptedStateExceptionsAttribute attribute.

In the .NET Framework versions 1.0 and 1.1, an unhandled exception that occurs in a thread other than the main application thread is caught by the runtime and therefore does not cause the application to terminate. Thus, it is possible for the UnhandledException event to be raised without the application terminating. Starting with the .NET Framework version 2.0, this backstop for unhandled exceptions in child threads was removed, because the cumulative effect of such silent failures included performance degradation, corrupted data, and lockups, all of which were difficult to debug. For more information, including a list of cases in which the runtime does not terminate, see Exceptions in Managed Threads.

To register an event handler for this event, you must have the required permissions, or a SecurityException is thrown.

For more information about handling events, see Consuming Events.

Other Events for Unhandled Exceptions"


For certain application models, the UnhandledException event can be preempted by other events if the unhandled exception occurs in the main application thread.

In applications that use Windows Forms, unhandled exceptions in the main application thread cause the Application.ThreadException event to be raised. If this event is handled, the default behavior is that the unhandled exception does not terminate the application, although the application is left in an unknown state. In that case, the UnhandledException event is not raised. This behavior can be changed by using the application configuration file, or by using the Application.SetUnhandledExceptionMode method to change the mode to UnhandledExceptionMode.ThrowException before the ThreadException event handler is hooked up. This applies only to the main application thread. The UnhandledException event is raised for unhandled exceptions thrown in other threads.

Starting with Microsoft Visual Studio 2005, the Visual Basic application framework provides another event for unhandled exceptions in the main application thread. See the WindowsFormsApplicationBase.UnhandledException event. This event has an event arguments object with the same name as the event arguments object used by AppDomain.UnhandledException, but with different properties. In particular, this event arguments object has an ExitApplication property that allows the application to continue running, ignoring the unhandled exception (and leaving the application in an unknown state). In that case, the AppDomain.UnhandledException event is not raised.








This is how to fix it.
GalacticPond

-Go to Control Panel
-Go to Programs and Features
-Go to the sidebar where it says "Turn Windows Features On or Off" (Or something to that
effect)
-Wait for the list to load
...
-Like a folder, next to each folder is a box. Each folder contains a subfolder.
If no subfolder is checked, the box should be empty
If some subfolders are checked, the box should have a black square.
If all subfolders are checked, the box should have a check.

-Go through all the folders and check them until all boxes are checked.
-Restart your computer as features required are applied.

-Shoot and Rob away at Gta VC