1. Due to disable in you UAC.

To fix it just simply go to your control panel in USER ACCOUNTS and enable the UAC.

note:- Never late your machine UAC disable…..it create a security hole. if someone suggest to disable UAC then it would be the most worst idea anyone can suggest you.

2. Feature of Gadget might be off.

To fix it go to control panel —> Program and Features

on the right of this window you can see the ‘Turn windows feature on or off’ click on it…and wait for while….it will take some time to load the contents….scroll down in this window you can see the ‘Windows Gadget Platform’ just make a check mark on it.viola…. now you can play with your gadget.

The Redmond company released Security Advisory 979682 to help customers mitigate the vulnerability until a patch is made available. The Windows NT #GP Trap Handler security hole, discovered and documented by Google engineer Tavis Ormandy, can potentially allow an attacker to elevate an existing account on a 32-bit (x86) Windows machine to full administrative privileges. This is nothing more than an Elevation of Privilege (EoP) vulnerability affecting the Windows kernel. It only impacts versions of 32-bit Windows, including XP, Vista and Windows 7. 64-bit (x64) Windows flavors are in no way affected.

User must not panic on this vulnerability because the risk associated with this vulnerability is extremely low. It is critical to note and the flaw cannot be exploited remotely. An attacker would already have to have access to a windows computer containing a vulnerable version of the operating system. Moreover, the attacker would also need access to an account on that computer.

so to help mitigate exploit of this vulnerability, users who do not require NT virtual DOS mode (NTVDM) or support for 16-bit application can disable the NTVDM. Here the steps necessary to disable the NTVDM subsystem.

1. Click Start—>Run—> type gpedit.msc n click on ok

this will open the Group Policy Console

2. Expand the Administrative Templates folder, and then click Windows Componets.

3. Click the Application Compatibility folder

4. In the details panel, Double click the Prevent access to 16-bit application policy setting. By default, this is set to Not Configured.

5.Change the policy setting to Enable, and then click OK.

Note:- After this User are not able to run 16-bit application….but still user want to use 16 bit application do similar process but at last click on disable on policy setting.

“In the Windows 7 “System and Security” control panel category, the Action Center lets you change User Account Control (UAC) settings. In the User Account Control Settings dialog box, you move the slide bar control for notifications, and then you click the OK button. In this scenario, the dialog box does not close, and no change is made. When the mouse pointer is positioned on the OK button, and you press ENTER, the dialog box still does not close, and no change is made,” Microsoft revealed.

Microsoft doesn’t offer a hotfix or an update designed to resolve this specific issue as of yet. However, the Redmond company does have a manual fix in place. Users will be required to essentially mend the problems created with the installation of Office 97 on top of Windows 7. Essentially, users need to put together a file that will modify the Windows 7 registry. For this, they will need nothing more than Notepad. They will need to create a file with the name UAC.reg and place it on the desktop. Next, they will have to copy and paste the following text in the UAC.reg file, save it and close the text editor.

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}”

After this, users will need to simply execute the UAC.reg file, and agree to all prompts presented by Windows 7. This is not a permanent fix, however. In case Office 97 is reinstalled, the UAC.reg file will have to run again in order to fix the registry problems.