none
Installing Office 97 breaks UAC setting UI in windows 7

    Question

  • Immediately after installing Office 97, I am no longer able to change the UAC level setting in the "User account control settings" dialog.

    I can move the slider bar to a different level up or down but there is no response whatsoever when the ok button is clicked. After un-installing Office 97 completely (I also used eraser97.exe after the normal uninstall process to ensure that it was competely removed), the "User account control settings" dialog no longer even appears when clicking on the "Change user account control settings" link from the Action center.

    From the research that I have done so far it seems that this is a common issue with people needing to use Office 97 and it may have something to do with a conflict between the macro protection system in Office 97 and the UAC implementation within Windows 7.

    It is still possible to change the UAC settings by making changes directly within the registry but this is less than ideal and shouldn't have to be necessary. I am always logged on as an Administrator and have tried this on 4 seperate computers with exactly the same result.
    Please note that I am not able in this case to upgrade to a later version of office. I am using only Access from Office 97 and this contains a particular feature that is absolutely necessary for me, that later versions of Access don't have.

    I fully understand that Office 97 is no longer supported by Microsoft, but I think that this is irrelevant in this case, as this is a Windows 7 bug when installing software that works correctly on Windows XP. Windows 7 should continue to work satisfactorily whether Office 97 is installed or not, just like any other legacy application. This is particulary true of core aspects such as the UAC.

    Note: Other than this issue Access 97 seems to work without problems on Windows 7.

    I would be grateful for some assistance with this issue.

    Monday, November 02, 2009 4:20 AM

Answers

  • Hi All,

     

    We have now worked out what the specific cause of this problem is.

    Office 97 makes many changes to the Windows registry when it is installed. This is to be expected of course.

    Unfortunately it changes some existing values in specific registry keys which are the cause of the issue. The changes were appropriate for older versions of windows but definitely not for Windows 7.

    What has worked for us is to back-up specific registry key values, install Office 97 and then restore these values.

    In each case it is the default value of the key that needs to be restored.

    The keys in question are:

    HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}

    HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}\NumMethods

    HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32

     

    HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}

    HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}\NumMethods

    HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32

     

    HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}

    HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}\NumMethods

    HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32

     

    HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}

    HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}\NumMethods

    HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32

     

    HKEY_CLASSES_ROOT\Interface\{B722BCC9-4E68-101B-A2BC-00AA00404770}\NumMethods

    HKEY_CLASSES_ROOT\Interface\{B722BCC9-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32

     

    HKEY_CLASSES_ROOT\Interface\{B722BCCA-4E68-101B-A2BC-00AA00404770}\NumMethods

    HKEY_CLASSES_ROOT\Interface\{B722BCCA-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32

     

    HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}

    HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}\NumMethods

    HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32

    Restoring the original default values of the last 3 keys shown above will in fact by itself restore the normal operation of the UAC settings user interface, but as the other keys are all closely related they should as a matter of course be restored also.

    Regards,

    John Van De Giessen


     

    Friday, November 20, 2009 10:36 AM
  • Hi John, 

    I add your fix here :)
     

    Below are the contents for a .reg file containing the original default values that we had in our particular case. If you copy the text into a file and name it with a .reg extension then double clicking on that file will set these values for you.
     --------------------------------------------------------------------------------------------------------------------------

    Windows Registry Editor Version 5.00

    [HKEY_CLASSES_ROOT]

    [HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}]
    @="IOleDocument"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}\NumMethods]
    @="6"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]
    @="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}]
    @="IOleDocumentView"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}\NumMethods]
    @="16"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]
    @="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}]
    @="IOleDocumentSite"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}\NumMethods]
    @="4"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]
    @="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}]
    @="IEnumOleDocumentViews"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}\NumMethods]
    @="7"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]
    @="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"

    HKEY_CLASSES_ROOT\Interface\{B722BCC9-4E68-101B-A2BC-00AA00404770}\NumMethods]
    @="6"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC9-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]
    @="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"

    [HKEY_CLASSES_ROOT\Interface\{B722BCCA-4E68-101B-A2BC-00AA00404770}\NumMethods]
    @="5"

    [HKEY_CLASSES_ROOT\Interface\{B722BCCA-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]
    @="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"

    [HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}]
    @="IOleCommandTarget"

    [HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}\NumMethods]
    @="5"

    [HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]
    @="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"

    ------------------------------------------------------------------------------------------------------------------------------


    Regards.
    Saturday, November 21, 2009 8:28 PM

All replies

  • Hi John,

    This is a compatibility issue of the application.  Please run the application using Windows 95 or Windows NT workstation compatibility mode.

    Please follow the below mention steps,
     1) Right click the exe and select the ‘properties’ option
     2) Select the Compatibility tab
     3) Select the “Run this program in compatibility mode for” check box
     4) Select the Windows XP SP2 from the drop down
     5) Click on Apply.

    Right-click the exe and Run as Administrator.

    I hope this will resolve this issue.  It would be more grateful if you could upgrade to the latest version of Office.

    Thanks,

    Anbu MS

    Tuesday, November 03, 2009 2:20 PM
    Moderator
  • Hi Anbu MS,

    Thankyou for the response. The problem however is not in the running of Access97; this actually runs just fine without having to set a compatibility mode, nor does it need to be run as administrator. (Trying these steps makes no difference at all)

    The problem with the windows 7 UAC setting UI exists whether Access97 is running or not. The problem exists simply because Office 97 (or any component of it) has been installed. 
    Just for additional information, if you reboot the system and DON'T run Access97 at all, the problem in the UAC settings UI still exists. I.e. It is not in running Access97 that the problem is caused.
    This very much appears to be a bug in the Windows 7 OS itself.

    Many thanks,

    John Van De Giessen
    Tuesday, November 03, 2009 11:46 PM
  • Isn't this situation exactly what "Virtual XP for Windows 7" is intended for?
    Wednesday, November 04, 2009 2:42 AM
  • Hi fanfarenj,

    Thank you for your thought on this.

    Windows XP Mode does not overcome this problem in all situations.
    The issues are here as as follows:
    1. XP Mode is not available for all editions of windows 7 and I cannot enforce which edition the users of my software will use. As a minimum Windows 7 Professional is required. I would recommend a minimum of the professional edition to our clients for other reasons anyway, but I cannot enforce it.
    2. XP Mode, even on supported editions of windows 7 has specific hardware requirements so that virtualization is supported - It may be some time before all users will have upgraded to suitable systems, particularly when their current systems are in other respects more than powerful enough to run windows 7.
    3. XP Mode is designed to allow older applications to run properly. Note that in this case the application, Access97, does run properly natively on Windows 7.
    This is clearly a bug in Windows 7 and I expect that anything short of a fix or workaround in the OS itself is not going to be a viable solution for this.

    Please all keep your thoughts coming though, they are greatly appreciated.

    Many thanks,

    John Van De Giessen

    Wednesday, November 04, 2009 3:14 AM
  • Well you make some valid points; but for all of these I can imagine a workaround. Of course that may involve a cost you are not willing to incur.

    If this is a critical issue I wouldn't wait for an answer to appear on this thread. I would contact Microsoft Technical Support.

    Wednesday, November 04, 2009 11:53 PM
  • John,

     I tried reproducing the issue, but UAC was working properly even after the installation of Office 97.  I would suggest you to restart the machine everytime you change the UAC settings.  If you don’t restart the machine after changing the UAC level, the changes won’t get reflected.

    Testing the changes in UAC settings:

    1)      Slide the UAC bar to the top, restart the machine and try changing the Date and Time settings (It will prompt a warning message)

    2)      Slide the UAC bar to the bottom, restart the machine and try changing the system settings (It won’t prompt any messages)

    Note: Sometimes, the change in UAC levels will not prompt the user to restart the machine.

    I hope this will resolve the issue.


    Thanks, M Anbu
    Friday, November 06, 2009 4:31 PM
    Moderator
  • I just tried installing Access 97 on a Windows 7 machine (32 bit), and have administrator rights.

    It originally failed to install because it couldn't place the system.mdw file in the Windows\System32 folder. When I ran Access 97, it complained that file was missing.  After I manually added that file to that folder (I was prompted for my user name and password), and ran Access 97 again, it fails with an out of memory error.  I suspect it needs rights to modify that file and Windows 7 isn't giving it to it.

    This error is unrelated to Windows 7 and is explained in http://support.microsoft.com/default.aspx/kb/161255. By installing the Office Developer Edition, it's up and running in Windows 7 (so far). 

    This was not meant to be a proposed answer but at least a confirmation that it can be done.

    FYI, I was able to apply the SR-1 Patch, but not SR-2 as the update chokes when it tries to modify the Tahoma font in the Windows folder.  So maybe I'm stuck with SR-1 instead of SR-2 on Windows 7.  Any suggestions for how to get around this would be appreciated.
    Friday, November 06, 2009 6:17 PM
  • Hi M Anbu,

    This is the first time that I have heard that someone hasn't encountered the problem with setting the UAC level after installing Office 97.

    Just to review our situation, Office 97 doesn't interfere in any way with the normal functioning of the UAC, just the ability to save the slider bar position in the setting user interface once the slider bar has been moved. In effect the "OK" button does not respond.
    If we change the UAC level by editing the registry then the UAC will work quite satisfactorily at that changed level. Even the slider bar in the settings user interface will correctly reflect the change if we set the level using this method. We just can't save the level by changing the slider bar in the settings user interface.

    Is there anyone else who has installed any part of Office 97 and doesn't have this issue?

    Many thanks,
    John Van De Giessen
    Saturday, November 07, 2009 11:55 PM
  • Hi LukeChung,

    The out of memory error occurs when installing from an original base level Office 97 install where the system has more than 1 Gigabyte of ram.
    Installing from a SR1 level install does not have this problem. Also, the problem is corrected after installing from an original base level install after applying service pack 1.

    To successfully install SR-2, you first need to extract the files from the service pack exe (it is an archive and can be extracted by something like Winzip) and then edit the file named filelist.txt. Remove all lines from it that refer to Tahoma and Comic sans font files. Run the sr2patch.exe from the extracted files and now it should succeed.

    Regards,
    John Van De Giessen
    Sunday, November 08, 2009 12:16 AM
  • John,

    I tried with different machines to reproduce this issue, but I couldn’t.   Office 97 doesn’t do anything with the UAC settings.  Please check whether the Office 97 has a valid license and make sure Windows 7 operating system has all the updates.

    After checking with the above mentioned, try reproducing the issue in different machines.

    Please post back if you face some issues.


    Thanks, M Anbu
    • Proposed as answer by M AnbuModerator Thursday, November 12, 2009 11:02 AM
    Thursday, November 12, 2009 11:02 AM
    Moderator
  • Hi M Anbu,

    Firstly let me thank you for your time and effort in this.

    Our Office 97 install is properly licensed and we are testing installs on both RC and RTM versions of Windows 7 which are activated and have all the updates applied.

    I am wondering if the difference between the problem occurring or not is in the edition and/or service pack level of the Office 97 installation. Ours may be different to yours.
    We have been using an "Office 97 Professional SR-1" edition install.

    I will try installing from a different edition and test the result; We have an original base level install that I can try. I will advise the result.

    Could you please advise which edition and service release level install that you are using?

    Many thanks,
    John Van De Giessen
    Friday, November 13, 2009 3:47 AM

  • John,

    Here are the edition and Service release I used for testing the issue,

    Operating system

    Windows 7

    Edition

    Enterprise

    Type

    64-bit Operating System

     

     

    Application

    Office 97

    Version

    8

    Edition

    Professional

    Language

    English - US

     


    Thanks, M Anbu
    Friday, November 13, 2009 9:48 AM
    Moderator
  • Hi M Anbu,

    This is the first time that I have heard that someone hasn't encountered the problem with setting the UAC level after installing Office 97.

    Just to review our situation, Office 97 doesn't interfere in any way with the normal functioning of the UAC, just the ability to save the slider bar position in the setting user interface once the slider bar has been moved. In effect the "OK" button does not respond.
    If we change the UAC level by editing the registry then the UAC will work quite satisfactorily at that changed level. Even the slider bar in the settings user interface will correctly reflect the change if we set the level using this method. We just can't save the level by changing the slider bar in the settings user interface.

    Is there anyone else who has installed any part of Office 97 and doesn't have this issue?

    Many thanks,
    John Van De Giessen
    I have the same problem. I use Windows 7 Professional 32bit and Office 97 Small Business Edition (all software is Original and Licenced of course...). I'm unable to change UAC setting with the  slider bar in control panel. No effect when click OK button. I can only change it using the system registry. Please help.
    Saturday, November 14, 2009 9:18 AM
  • M Anbu,

    I have tried installing from a different edition of Office 97 but still get the same problem in the UAC settings user interface.

    I notice that you are testing the installation on a 64 bit version of windows 7.
    Would it be possible for you to try installing Office 97 an a 32 bit install of Windows 7 and see what results you get?

    Many thanks,
    John Van De Giessen
    Tuesday, November 17, 2009 6:10 AM
  • John,

    As mentioned earlier, i tested the application with different machines.  I have tried with Windows 7 32 bit and Windows 7 64 bit Operating systems.
    Please check whether some other applications installed is affecting the UAC settings.  Check with the firewall of the machine as well.

    Here are the edition and Service release I used for testing the issue,

    Operating system

    Windows 7

    Edition

    Enterprise

    Type

    32-bit Operating System

     

     

    Application

    Office 97

    Version

    8

    Edition

    Professional

    Language

    English - US

     

    Tuesday, November 17, 2009 11:57 AM
    Moderator
  • Hi again Anbu,

    It's very strange that you have no problems...i have only few programs installed atm on my machine:


    Adobe Flash player 10
    Avira Antivir Personal
    Crysis single player DEMO
    EVGA Precision 1.8.1
    Foxit Reader
    Google Chrome
    Java 6 update 17
    Microsoft Excel 97
    Microsoft Excel Euro Toolbar Addin
    Microsoft Visual C++ 2005 and 2008 (with updates)
    Microsoft Word 97
    Microsoft Silverlight
    Nvidia Drivers
    Nvidia PhysX
    OpenOffice 3.1
    Opera 10.01
    Quicktime alternative 3.0.1
    Total Commander
    TeamSpeak 2 RC2
    Windows Live Essentials
    Juris Data (software for my profession)

    That's all. Somes of these softwares were installed after  the problem was found. My Windows 7 is updated of course. My Office 97 is "Small Business Edition".
    Searching on the web i found some peoples with the same issue.
    Any ideas?

    Sorry for my english anyway.





    Tuesday, November 17, 2009 5:34 PM
  • Hi All,

    There is another thread within social.technet.microsoft.com which is discussing this problem, where a number of people are having the same issue.

    For your reference the thread is titled: Restore Points delete & UAC won't change
    http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/4175502c-13fc-4da8-84d9-db8c8cc3da9a

    This is certainly not an isolated issue. There are also discussions on other forums regarding this same issue, none of which have yet proposed a viable solution.
    I have seen at least one post from a corporate administrator who also has this issue across all the corporate workstations.
    The common aspect of all of the threads that I have looked at is that the problem occurs immediately after installing Office 97.

    M Anbu however, has been able to install Office 97 on a number of machines without seeing this issue occur. One notable aspect here is that in his testing, Office 97 has been installed on 32 bit and 64 bit versions of Windows 7 Enterprise.

    Is it possible that the Enterprise edition of Windows 7 handles some things differently enough to prevent this glitch from occurring?

    Regards,

    John Van De Giessen

    Wednesday, November 18, 2009 2:55 AM
  • Hi All,

     

    We have now worked out what the specific cause of this problem is.

    Office 97 makes many changes to the Windows registry when it is installed. This is to be expected of course.

    Unfortunately it changes some existing values in specific registry keys which are the cause of the issue. The changes were appropriate for older versions of windows but definitely not for Windows 7.

    What has worked for us is to back-up specific registry key values, install Office 97 and then restore these values.

    In each case it is the default value of the key that needs to be restored.

    The keys in question are:

    HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}

    HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}\NumMethods

    HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32

     

    HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}

    HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}\NumMethods

    HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32

     

    HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}

    HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}\NumMethods

    HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32

     

    HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}

    HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}\NumMethods

    HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32

     

    HKEY_CLASSES_ROOT\Interface\{B722BCC9-4E68-101B-A2BC-00AA00404770}\NumMethods

    HKEY_CLASSES_ROOT\Interface\{B722BCC9-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32

     

    HKEY_CLASSES_ROOT\Interface\{B722BCCA-4E68-101B-A2BC-00AA00404770}\NumMethods

    HKEY_CLASSES_ROOT\Interface\{B722BCCA-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32

     

    HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}

    HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}\NumMethods

    HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32

    Restoring the original default values of the last 3 keys shown above will in fact by itself restore the normal operation of the UAC settings user interface, but as the other keys are all closely related they should as a matter of course be restored also.

    Regards,

    John Van De Giessen


     

    Friday, November 20, 2009 10:36 AM
  • Hi John, 

    I add your fix here :)
     

    Below are the contents for a .reg file containing the original default values that we had in our particular case. If you copy the text into a file and name it with a .reg extension then double clicking on that file will set these values for you.
     --------------------------------------------------------------------------------------------------------------------------

    Windows Registry Editor Version 5.00

    [HKEY_CLASSES_ROOT]

    [HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}]
    @="IOleDocument"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}\NumMethods]
    @="6"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC5-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]
    @="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}]
    @="IOleDocumentView"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}\NumMethods]
    @="16"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC6-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]
    @="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}]
    @="IOleDocumentSite"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}\NumMethods]
    @="4"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC7-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]
    @="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}]
    @="IEnumOleDocumentViews"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}\NumMethods]
    @="7"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC8-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]
    @="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"

    HKEY_CLASSES_ROOT\Interface\{B722BCC9-4E68-101B-A2BC-00AA00404770}\NumMethods]
    @="6"

    [HKEY_CLASSES_ROOT\Interface\{B722BCC9-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]
    @="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"

    [HKEY_CLASSES_ROOT\Interface\{B722BCCA-4E68-101B-A2BC-00AA00404770}\NumMethods]
    @="5"

    [HKEY_CLASSES_ROOT\Interface\{B722BCCA-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]
    @="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"

    [HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}]
    @="IOleCommandTarget"

    [HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}\NumMethods]
    @="5"

    [HKEY_CLASSES_ROOT\Interface\{B722BCCB-4E68-101B-A2BC-00AA00404770}\ProxyStubClsid32]
    @="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"

    ------------------------------------------------------------------------------------------------------------------------------


    Regards.
    Saturday, November 21, 2009 8:28 PM
  • I had the some problem...couldn't change the uac slider. I could move it, but clicking OK did nothing and it would always revert to default. I do not have Access97 on my machine. My installation does, however, include Office 93 Small Business Edition. Nonetheless, I restored the registry and it worked for me, also. 
    Saturday, December 19, 2009 9:01 PM
  • MSFT provides a KB article about this:

    http://support.microsoft.com/kb/978591/ - You cannot change User Account Control (UAC) settings on Windows 7

    MS provides a reg file to resolve that issue, which does the same like the file from the user Arcangelo Gruosso.

    André
    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Sunday, December 20, 2009 1:25 PM
  • Hi John,
    I too do NOT have the problem.

    Am running Windows 7 Ultimate (64-bit version) and installed the full suite of programs in Office 97. I am able to change the UAC setting at will (using the slider bar), and any changes are reflected and remain until I change them again. No problem.

    Going in and making wholesale changes in the registry is only inviting problems, in my opinion.

    Regards,
    Trent Fargo
    Sunday, January 24, 2010 4:48 PM
  • Hi Trent,

    Microsoft have now officially accepted that this is an issue and have posted the same solution that I have come up with in their knowledge-base at http://support.microsoft.com/kb/978591
    Hence this has now become the official Microsoft supported solution.

    It is possible that the reason you have not seen this problem is that some other software that you have installed since installing Office 97 may have set these registry entries back to their correct values. 
    Either way this is without doubt a widespread issue.

    In general I agree with your opinion about "Going in and making wholesale changes in the registry is only inviting problems" but this situation is quite different; It is the Office 97 install that is making these wholesale changes and this solution is about restoring them back to what Windows 7 expects them to be.

    Regards,
    John Van De Giessen


    Thursday, January 28, 2010 3:54 AM
  • Hi,

    I am running Windows Xp 64Bit and I try zu install Access97 from the Office97 CD. When I start the setup.exe Windows show me an error.
    It is not impossible to install this Software on a 64Bit System.

    How can I install this? Some people have it installed.

    Michael
    Monday, February 08, 2010 10:56 AM
  • Hi pcmedv -

    You did not specify what the error Windows was showing you, but I did find an installation problem with Office Pro 97 on Windows XP.

    If your problem had to do with: Htmlmarq.ocx unable to register istself in sys reg, this was apparently because Windows XP Service Pack 2 disabled the HTMLmarq.ocx Active X feature for security reasons.

    If this is the case, check out this forum for a solution: http://forums.techarena.in/office-setup/92349.htm

    Bruce
    Sunday, March 14, 2010 1:41 AM
  • John,

     

    Is it possible that 97 also messes up the values that impact Windows Installer and Creating restore points? I had (for a consulting job) the company I was working for add Visio 97 on my Windows 7 machine and these 2 functions don't work anymore. It has been uninstalled since. Thanks.

     

    Jay

    Thursday, June 03, 2010 1:26 PM
  • Hi Jay,

     

    I haven't experienced a problem in this area, not yet at least.

     

    Has anyone else found this to be an issue?

     

    Regards,

    John

    Monday, June 07, 2010 7:32 AM
  • This doesn't work for me.  So I am at SR1 still.  I have Office 97 professional and Window 7 Ultimate.  I also can't create a System.mdw, and one from my other machine doesn't satisfy msaccess. 

    I really believe Microsoft should have done better.  I had no problems running this version on XP and Microsoft could have darn well fixed the Service paks to not need altering, or post good directions on getting the service paks to load.

    I'm a retired IT professional and am having multiple problems with Window 7.  What are the non professionals going to do?

    Friday, June 25, 2010 10:51 PM
  • I really believe Microsoft should have done better.  I had no problems running this version on XP and Microsoft could have darn well fixed the Service paks to not need altering, or post good directions on getting the service paks to load.

    You're using an completely outdated software. This is not the fault of MS. Upgrade to 2007/2010 which are both supported on Windows 7. Office XP and 2003 work, but this is not officially supported by MS.

    Look at Apple, the don't support software which is older than 2 years. MS has one of the best and longest software support you can find.


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Saturday, June 26, 2010 12:38 PM
  • On Sat, 26 Jun 2010 12:38:04 +0000, Andre.Ziegler wrote:
     
    > I really believe Microsoft should have done better. I had no problems running this version on XP and Microsoft could have darn well fixed the Service paks to not need altering, or post good directions on getting the service paks to load.
    >
    > You're using an completely outdated software. This is not the fault of MS.
     
     
     
    I agree with the above, but let me add the following:
     
    Any time someone is running an old version of an program, and is
    considering changing to a newer version of Windows, it is incumbent
    upon him to first find out whether his programs will be compatible
    with the new Windows. Not to do is looking for trouble.
     
    In fact, it's appropriate to do this with all your software, not just
    older versions. You are more likely to have problems with older
    versions, but you can have incompatibility issues with anything.
     
    Not to check first is like buying a new bigger refrigerator to replace
    your old one with first checking to see whether it will fit into the
    space in your kitchen.
     
     
     

    Ken Blake
    • Proposed as answer by invictagunner Monday, August 23, 2010 2:38 PM
    Saturday, June 26, 2010 2:52 PM
  • This is a very useful article for anyone wanting to run Access 97 on Windows 7 especially if the intention is to also load Office 2007 or 2010 in addition to Access 97.

     

    I have successfully installed Access 97 starting from the Office 97 Professional CD for SR-1.

     

    The level of Windows 7 (64 bit Professional Version) was as installed on a new Dell machine in July 2010.

     

    I then loaded Office 2007 as the main office system. As mentioned elsewhere the requirement to also load Access 97 is often dictated by the need to maintain legacy applications which continue to be run very successfully at this level of software under Windows XP or similar.

     

    The full procedure and list of problems overcome is as follows:-

     

    1)     Make a custom installation of Office 97 into an Office97 folder selecting only Access and its associated data utilities.

    2)     The error message CTL3D32.DLL not correctly installed – must be installed in the Windows System Directory can be ignored. Should find it is already in the Windows\System32 directory.

    3)     If you now run the SR-2b update (SR2bOF97.EXE) for Office 97 it will fail unless you do the following:-

    a.      create two new temporary folders – say folder97 and foldersavefonts

    b.      copy the windows fonts relating to tahoma and comic (4 files) from \windows\fonts to foldersavefonts.

    c.      extract the files from SR2bOF97.EXE to folder97 using Winzip or similar.

    d.      select the four font files relating to Tahoma and comic and right click to then install these fonts in Windows 7.

    e.      if you do not do the above the SR-2 install fails because of a version problem with the fonts.

    f.       now run SR2bOF97.EXE in the normal way. It should be successful – if not the situation is different to mine and the log will need to be viewed to troubleshoot the problem

    g.      finally go to foldersavefonts and install these fonts back into Windows 7.

    4)     It is now recommended to run the Jet3 patch Jet35sp3.exe which can be downloaded from Microsoft.

    5)     At this point you should have a fully working Access 97 system. This procedure should also work for Word, Excel and Powerpoint but not Outlook.

    6)     Now install Office 2007/10 as required preferably a custom installation into an Office20xx folder.

    7)     If you have installed Access 20xx there will be a conflict between the Access 97 and 20xx installations. Both version work fine (ignore the message to rerun setup) once loaded but Access 97 will need to be run with Administration permissions (right click the short cut and click administrator) after running Access 20xx. In a similar way Access 20xx will rerun its registration processes after running Access 97. This situation occurs whenever you move between the versions unless you follow the following steps.

    8)     Load Access 20xx to ensure that it is registered.

    9)     Use notepad to create an empty file MSACCESS.SRG – suggest in folder97

    10)  find the Microsoft supplied MSACCESS.SRG – this is installed in the folder name specified in the custom install of Office 20xx. Rename this file to MSACCESS.SRG.SAV.

    11)  Copy in the empty MSACCESS.SRG from folder97 to replace the correct version.

    12)  This trick seems to prevent the conflict between Access 97 and Access 20xx. Remember if any reinstall work is needed for Office 20xx to reinstate the Microsoft supplied version.

    13)  The original subject of this thread seems to have been corrected in currently shipped builds of Window 7. If the problem does appear there is a Microsoft supplied fix for the problem. http://support.microsoft.com/kb/978591/

    14)  Finally, in case anyone needs to make a clean start in new folders. I have also found that the above procedures are still repeatable after standard uninstalls of both Office 97 and Office 20xx

    15) If ISAM problems occur with txt or .xls files it is likely that the .DLLs need to be manually registered. To do this use the command line and type C:\windows\syswow64\regsvr32.exe c:\windows\syswow64\mstext35.dll. This will register mstext35.dll. Then type:- :\windows\syswow64\regsvr32.exe c:\windows\syswow64\msexcl35.dll. This will register msexcl35.dll

     

     

     

    If anyone finds additional problems or information would be pleased to see them posted here.

     

    • Edited by invictagunner Monday, August 23, 2010 11:35 PM Added ISAM issues
    Monday, August 23, 2010 2:40 PM
  • I have a Lenovo v570 with Windows 7 64 bit installed. I load in Microsoft Office 97 and it worked just fine. I had no trouble changing the UAC.

     

    Bluebird

    Tuesday, September 06, 2011 1:30 AM
  • >>  I have a Lenovo v570 with Windows 7 64 bit installed. I load in Microsoft Office 97 and it worked just fine. I had no trouble changing the UAC.

    Yes, this is only an issue with 32bit Windows 7.    

    64bit windows 7 does not use the same registry settings in this case and so does not have this issue.

    John

    Friday, November 18, 2011 12:54 AM