Here is the procedure.

1. Get to RUN—>  and Type %APPDATA%\Microsoft\Windows\Recent\AutomaticDestinations then Press Enter.

2. Here opens a new Windows with the files names. likes .1b4dd67f29cb1962.automaticDestinations-ms

 

3. Clear all the files on this folder…..and then try to visit your folder…..now you will start to see the jumplist in the explorer icon as well on others too.

Yes, Windows has released the Application Compatibility update withc improves the combatibility experience. The company notes that the update is designed to integrate with not only Windows 7, but also Windows Vista Service Pack 2 (SP2), Windows Server 2001 Service Pack 2 (SP2), and Windows Server 2008 R2. In New OS of  Windows when you try to install and run Certain Legancy Games of applications you may experience one or more of the folowing symptoms:

The game, the application, or the firmware is installed incorrectly. The game, the application, or the firmware causes system instability. The primary functions of the game, of the application, of the firmware does not work correctly.

There are no less than three modifications that Microsoft can introduce through an application compatibility update. Incompatible application are placed under a Hard Block, which Prevents them from running on the operating system. Also for incompatibile application, the Redmond company can use a Soft Block which only informs users of the incompatibility issues. At the same time, the refresh can update functionlaity for applications running on top of the Operating Systems.

List of those applications that are included in the Feb 2010 Update are available in KB976264.

 All supported x86-based versions of Windows Vista
- All supported x64-based versions of Windows Vista

- All supported x86-based versions of Windows Server 2008
- All supported x64-based versions of Windows Server 2008
- All supported IA-64-based versions of Windows Server 2008

- All supported x86-based versions of Windows 7
- All supported x64-based versions of Windows 7

- All supported x64-based versions of Windows Server 2008 R2
- All supported IA-64-based versions of Windows Server 2008 R2

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.

When they install Windows 7 on the Computer, a black screen does appear during the installation process. that’s the problem…..but the installation under goes inside the black screen. and at this situation, you may not be able to complete installation.

Here some list of AMD/ATI Radeon GPU’s that are affected by this issues mentioned above.

ATI Mobility Radeon HD 4650 (PCI\VEN_1002&DEV_9480); ATI Mobility Radeon HD 4670 (PCI\VEN_1002&DEV_9488); ATI Mobility Radeon HD 4870 (PCI\VEN_1002&DEV_945A); ATI Mobility Radeon HD 4850 (PCI\VEN_1002&DEV_944A) and ATI Mobility Radeon HD 4330 (PCI\VEN_1002&DEV_9552).

Also looking at the solution for this problem….i have found the solution…., this is basically for the advanced users involving the AutoUnattend.xml answer file and the latest graphics driver and a USB flash drive. Copy the uncompressed graphics driver on the USB flash drive. To do this, follow these steps:

Download the latest driver for your graphics adapter from the AMD Web site. Run the downloaded program (.exe) to extract the driver. The program will prompt for an installation location, such as c:\ati\support\. After the extraction is complete, locate the installation folder that is noted in the previous step. Copy the installation folder onto the USB flash drive.

Users will also need to create the AutoUnattend.xml answer file, by opening a Notepad file and copy the text highlighted in blue color below. This file has to be saved as AutoUnattend.xml using the UTF-8 encoding format, and then i needs to be copied to the root of the USB. Now From the Windows 7 installation DVD, start the computer that has the AMD Radeon GPU that uses eDP.Immediately connect the USB flash drive after the computer starts from DVD. Follow the instructions to complete the installation process. When the system restarts for the first time, disconnect the USB flash drive.

Here is the text for the AutoUnattend.xml answer file just copy, Paste and save the file as mentioned above.

<?xml version=”1.0″ encoding=”utf-8″?>

<unattend xmlns=”urn:schemas-microsoft-com:unattend”>

<servicing></servicing>

<settings pass=”windowsPE”>

<component name=”Microsoft-Windows-PnpCustomizationsWinPE” processorArchitecture=”x86″ publicKeyToken=”31bf3856ad364e35″ language=”neutral” versionScope=”nonSxS” xmlns:wcm=”http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>

<DriverPaths>

<PathAndCredentials wcm:keyValue=”1″ wcm:action=”add”>

<Path>%configsetroot%</Path>

</PathAndCredentials>

</DriverPaths>

</component>

<component name=”Microsoft-Windows-Setup” processorArchitecture=”x86″ publicKeyToken=”31bf3856ad364e35″ language=”neutral” versionScope=”nonSxS” xmlns:wcm=”http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>

<UseConfigurationSet>true</UseConfigurationSet>

</component>

<component name=”Microsoft-Windows-PnpCustomizationsWinPE” processorArchitecture=”amd64″ publicKeyToken=”31bf3856ad364e35″ language=”neutral” versionScope=”nonSxS” xmlns:wcm=”http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>

<DriverPaths>

<PathAndCredentials wcm:keyValue=”1″ wcm:action=”add”>

<Path>%configsetroot%</Path>

</PathAndCredentials>

</DriverPaths>

</component>

<component name=”Microsoft-Windows-Setup” processorArchitecture=”amd64″ publicKeyToken=”31bf3856ad364e35″ language=”neutral” versionScope=”nonSxS” xmlns:wcm=”http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>

<UseConfigurationSet>true</UseConfigurationSet>

</component>

</settings>

<settings pass=”offlineServicing”>

<component name=”Microsoft-Windows-PnpCustomizationsNonWinPE” processorArchitecture=”x86″ publicKeyToken=”31bf3856ad364e35″ language=”neutral” versionScope=”nonSxS” xmlns:wcm=”http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>

<DriverPaths>

<PathAndCredentials wcm:keyValue=”2″ wcm:action=”add”>

<Path>%configsetroot%</Path>

</PathAndCredentials>

</DriverPaths>

</component>

<component name=”Microsoft-Windows-PnpCustomizationsNonWinPE” processorArchitecture=”amd64″ publicKeyToken=”31bf3856ad364e35″ language=”neutral” versionScope=”nonSxS” xmlns:wcm=”http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>

<DriverPaths>

<PathAndCredentials wcm:keyValue=”2″ wcm:action=”add”>

<Path>%configsetroot%</Path>

</PathAndCredentials>

</DriverPaths>

</component>

</settings>

<settings pass=”auditSystem”>

<component name=”Microsoft-Windows-PnpCustomizationsNonWinPE” processorArchitecture=”x86″ publicKeyToken=”31bf3856ad364e35″ language=”neutral” versionScope=”nonSxS” xmlns:wcm=”http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>

<DriverPaths>

<PathAndCredentials wcm:keyValue=”3″ wcm:action=”add”>

<Path>%configsetroot%</Path>

</PathAndCredentials>

</DriverPaths>

</component>

<component name=”Microsoft-Windows-PnpCustomizationsNonWinPE” processorArchitecture=”amd64″ publicKeyToken=”31bf3856ad364e35″ language=”neutral” versionScope=”nonSxS” xmlns:wcm=”http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>

<DriverPaths>

<PathAndCredentials wcm:keyValue=”3″ wcm:action=”add”>

<Path>%configsetroot%</Path>

</PathAndCredentials>

</DriverPaths>

</component>

</settings>

<cpi:offlineImage cpi:source=”wim:d:/sources/install.wim#Windows 7 ULTIMATE” xmlns:cpi=”urn:schemas-microsoft-com:cpi” />

</unattend>

If you have a dual-boot system with Linux and Windows, then you probably know that when you start your system first Linux boot loader appears showing Linux as well as Windows boot entries and if you select Windows from the list, it starts Windows.

Suppose a situation when you want to remove Linux from your system and want to use only Windows, then how will you do it?

Many times people delete the partitions having Linux installed from “Disk Manager” but it doesn’t remove Linux completely. The Linux boot loader still appears at startup but since you deleted Linux partitions, the boot loader gets corrupted and your system becomes unusable.

So if you are also facing this problem or you faced this problem in past and could not get a working solution, then read this tutorial and you can follow it if you find yourself in a similar situation.

This tutorial will help you in completely removing Linux from a dual-boot system:

1. First you’ll need to boot using Windows setup CD. You can use Windows 98 Setup CD or Windows 2000, XP, 2003  CD or Windows Vista, Server 2008 DVD.

A. Using Windows 98 CD:

Boot into Command Prompt and provide following command:

fdisk /MBR

Now exit from command prompt by typing Exit and press Enter.

B. Using Windows 2000, XP, 2003 CD:

Enter into “Recovery Console” by pressing “R“, select your Windows installation and enter administrator password. Now provide following command:

fixmbr

Press “Y” to confirm and type Exit to exit from recovery console.

C. Using Windows Vista, Server 2008 DVD:

Boot using setup DVD and click on “Repair Computer” link, then click on “Command Prompt”. Now navigate to your DVD drive using CD command and at last provide following command:

bootsect /nt60 SYS /mbr

Exit from Command prompt and restart your system.

Thanks to Ramesh Kumar (Fellow MVP) to provide this trick.

2. The above commands will remove the Linux boot loader from startup and you’ll be able to directly boot into Windows.

3. If you have not deleted Linux partitions, then you can delete them using “Disk Manager” tool in Windows.