When a virus is located on your computer the first thing you should do is run a full system scan on your computer to see if your internet security software is picking up any virus's.
The top virus removal security software are:-
Microsoft Security Essentials
AVG free edition
AVG Pro
Norton Internet Security
McAfee
If full system scan of your computer have failed to remove the virus from your system then you have definitely got a horrible virus on your computer and you will manually have to delete the infected files.
This example is how to remove antivirus 2011
1) Open task manager (ctrl + Alt + Delete) and "end process" to av2011.exe
2) WARNING!! Open Regedit (Start, type/select "run" and then type 'regedit"
ii) Locate HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run "av2011.exe" and delete all components of "av2011.exe"
iii) Exit out of regedit
3) Remove existing traces of av2011:
ii) Go to programs, right click on av2011 and open file located. Delete ALL files in this folder.
iii) Go to control panel select add or remove program and if you locate av2011 uninstall the program off your system
Finally Restart your machine
Friday, July 22, 2011
Simple Ways to Make Windows 7 Run Faster at Startup [download os]
windows 7 might be the newest version of Windows but it’s already extremely popular. There are a lot of great things that you can say about Windows 7 compared to earlier Windows operating systems, but it’s not perfect, and you’ll still need to know how to fix windows 7 run faster at startup. There are unfortunately a number of errors and problems which can affect the operating system .A slow startup problem may be a headache for all computer users. After using Windows 7 for some time, I find that we can make Windows 7 run faster with some rather simple tricks.
1. Increase Windows 7 boot speed
Below are the steps to fix slow Windows 7 boot problem
a. Press "[WIN] +R" to open Run window.
b. Select "Timeout" tab within "Boot".
2. Disable Prefetcher to make Windows 7 run faster
Below are the steps to fix slow Windows 7 boot problem
a. Press "[WIN] +R" to open Run window and type "regedit" to open Registry Editor.
3. Speed up Windows 7 at startup
We know that when booting up computers or run a program, it will call for some related data. If the files are too fragmented, it will take more time for hard disk head to move too much to reach what it needs like finding stuff from a messy warehouse. To ensure a faster startup, a regular disk defragment process is needed. By the way, it is recommended to uninstall the unneeded programs and clear the useless files before.
1. Increase Windows 7 boot speed
Below are the steps to fix slow Windows 7 boot problem
a. Press "[WIN] +R" to open Run window.
b. Select "Timeout" tab within "Boot".
c. If you have installed Windows operating system, you can set it to 3s from the default 30s; if you install multiple operating systems, set the value to the desired seconds you would like to have at boot time and then check "No GUI Boot" tab.
d. Click "Advanced Options" to set the "Number of processors" according to your computer configuration. After the simple setting here, you will see an improvement on Windows 7 boot speed.
2. Disable Prefetcher to make Windows 7 run faster
Below are the steps to fix slow Windows 7 boot problem
a. Press "[WIN] +R" to open Run window and type "regedit" to open Registry Editor.
b. Locate HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSessionManager Memory ManagementPrefetchParameters and right click "PrefetchParameters" on the left-hand side, change its value data from "3" to "0".
3. Speed up Windows 7 at startup
We know that when booting up computers or run a program, it will call for some related data. If the files are too fragmented, it will take more time for hard disk head to move too much to reach what it needs like finding stuff from a messy warehouse. To ensure a faster startup, a regular disk defragment process is needed. By the way, it is recommended to uninstall the unneeded programs and clear the useless files before.
How to fix "BOOTMGR is Missing" error [download os]
Windows requires the "BOOTMGR" file to load the operating system when you turn on the computer. The “Bootmgr is Missing” Error is a problem that indicates your computer could not locate your Windows installation. The most common reasons for BOOTMGR errors include corrupt and misconfigured files, hard drive and operating system upgrade issues, corrupt hard drive sectors. You can correct the error using the Windows 7 installation DVD, which contains a bootup repair module for corrupted or missing boot files.
Steps to Fix "BOOTMGR is Missing" error
• Insert the Windows 7 installation DVD in the computer's drive. Press the "Reset" button on your computer's case to reboot the computer. When the command prompt asks if you want to boot to the DVD, press any key to open the Windows 7 installation window
Select your language, time zone and keyboard settings in the first installation window. Click "Next."
• Click the "Repair Your Computer" link at the bottom-left corner in the next window. The list of repair options display on the next screen.
• Click the "Startup Repair" option. Windows searches for any corrupt or missing boot files including BOOTMGR. The missing file is replaced on the hard drive. After the repair process completes, remove the installation DVD and reboot the computer.
How to Change Programs at Windows Startup [download os]
One of the main reasons why your Windows takes so long to boot when you switch it is due to the number of programs that run at system startup and this is the place for you to identify and disable them. In Windows operating systems, certain Terminate and Stay Resident (TSR) programs are initiated during startup. Often, users will need to modify the startup process to stop the loading of some TSR programs. A Windows utility program, the System Configuration Utility (msconfig), is provided with each operating system installation. This utility will enable the user to modify the Windows startup process and the programs initiated during this process.
Steps to change programs at windows startup
• Click the "Start" button on the Windows desktop.
• Select the "Run" option.
• Type "msconfig" into the Run input box.
• Click "OK." A window with five tabs will appear.
• Click the "Startup" tab. A list of programs with checkboxes will appear.
• Uncheck each unneeded startup program. By using the msconfig utility, changes made to the startup process may be easily reversed.
• Reboot the computer. Windows will now start only the TSR programs specified with the configuration utility.
Many of you may have already have your hands on Windows 7 and must be exploring it. Waiting for your Windows to shut down completely can be a frustrating if you want the shutdown time to be much faster than what it is now read our blog “How to speed up shutdown time in windows 7”
How to Invite Remote Assistance on Windows 7 [download os]
When something goes wrong with the computer, and you don’t know how to fix the issue. So, you try to contact somebody for help. For this Windows has created Windows Remote Assistance feature, which allows to anyone, with your permission of course, connect remotely to a computer via a local network or the internet. You must invite the remote person before a connection can take place. Use the Easy Connect method if the other person is also using a Windows 7 computer. After the initial successful connection, the person appears in a contact list to simplify future invitations. Create and send an invitation file if the other person is using a different version of Windows.
Steps to send Invitation File• Click the "Start" and type "Remote Assistance" in the "Search" box.
• Select "Windows Remote Assistance" from the list that appears.
• Click "Invite someone you trust to help you."
• Click "Save this invitation as a file" and select "Desktop" as the save location.
• Use your regular email program or website to send the file from the Desktop to the remote person.
• Communicate the 12-character password that appears to the remote support person, who will use it to connect to your computer when they open the invitation file. Click "Yes" to accept the connection.
Easy Connect
• Click the "Start" button and then type "Remote Assistance" in the "Search" box.
• Select "Windows Remote Assistance" from the list that appears.
• Click "Invite someone you trust to help you."
• Click "Use Easy Connect."
• Communicate the 12-character password to the remote support person, who will use it to connect to your computer through Easy Connect. Click "Yes" to accept the connection
Windows Vista Stops Responding While Trying to Boot [download os]
Windows vista is considered as the most secure and the reliable Operating system. But at the same time bugs and the errors can't be ruled out. That’s the reason we face problems in Windows Vista. One of the typical symptoms is that computer might fail to boot, displaying STOP errors on screen. This issue can occur if any one of the file required to boot the system is missing or damaged. To fix this issue you need to reinstall windows vista and restore the information from current data backup. If you facing problem with your backup, scan your hard drive using commercial data recovery applications or contact Windows Vista Technical Support .
Steps to follow if Windows Vista Stops Responding While Trying to Boot
• To fix this issue, you should have Windows Vista installation disc.
• Insert the installation disc and boot your system
• select the desired language and click on “Next”.
• Select 'Repair your computer' option
• You need to then select the operating system to be repaired in 'System Recovery Options' dialog box
• In the same dialog box, click to choose 'Startup Repair' option
• Startup Repair will automatically try to detect and correct startup problems that prevent Windows Vista from booting. Click Finish when the process gets completed.
Windows Vista Problems and Troubleshooting [download os]
This vista problem troubleshooting article guide you how to troubleshoot various windows vista error problem and in detail windows vista troubleshooting solution.
There are lots of problems with windows vista and those are vary difficult to troubleshoot for a layman user. Here are the list of windows vista problems and troubleshooting guide for those vista problems.
Vista problem kernel data inpage error status no such device
During re-enumeration of a previously enumerated ide controller, a race condition exists between atapisys and pciidexsys or between Ataportsys and Pciidex.sys. In this race condition, the following conditions are true:
Atapi.sys and Ataport.sys use the stm method to select a transfer mode on a channel. The stm method is in the advanced configuration and power Interface bios. pciidex.sys verifies whether that channel exists by checking for the ide decode enable bit.
If the bios implementation of the stm method has cleared the ide decode enable bit, pciidex.sys determines that the channel does not exist. When this behavior occurs, pciidexsys does not enumerate the channel.
vista troubleshooting guide for this error
Because atapisys and ataportsys never run the stm method as long as there is i o on the channel, the stm method does not have to clear the ide decode enable bit. Therefore, BIOS manufacturers should not clear the ide decode enable bit in the stm method.
Path maximum transmission unit black hole router detection.The following is a list of black hole router detection changes that are included in windows server 2003 sp2.
By default, black hole detection is turned on.
Black hole probing is performed only for connections in established or advanced states.
Black hole probing is performed only for connections on which there is no full-size segment acknowledgement.
If black hole probing fails, the tcp maximum segment size of the connection is restored to what it used to be before probing.
• With black hole router detection turned off in versions of Windows that are earlier than windows server 2003 sp2, a connection times out approximately after 63 rtt. In windows server 2003 sp2, connections time out after 71 * rtt.
Remove Hibernation in Windows Vista troubleshooting
Hibernation is not made unavailable when you set the value of the hibernate after setting to never by using the power options item in windows vista control panel.
To make hibernation unavailable on windows vista, follow these steps:
1. Click start, and then type cmd in the start search box.
2. In the search results list, right-click command prompt, and then click run as administrator.
3. When you are prompted by user account control, click continue.
4. At the command prompt, type powercfg.exe hibernate off, and then press enter.
5. Type exit, and then press enter.
To make hibernation available, follow these steps for vista troubleshooting:
1. Click start on windows vista, and then type cmd in the start search box.
2. In the search results list, right-click command prompt, and then click run as administrator.
3. When you are prompted by user account control, clicks continue.
4. At the command prompt, type powercfg.exe hibernates on, and then press enter.
5. Type exit, and then press enter to close the command prompt window.
This tutorial will take a look at the “Hyper-v Manager” built-in to Windows Server 2008 R2. !! For this to work your computers/servers CPU will have to support hardware assisted “Virtualization” and have it enabled in the BIOS. !!
Related Microsoft Windows Server Guide Articles
There are lots of problems with windows vista and those are vary difficult to troubleshoot for a layman user. Here are the list of windows vista problems and troubleshooting guide for those vista problems.
Vista problem kernel data inpage error status no such device
During re-enumeration of a previously enumerated ide controller, a race condition exists between atapisys and pciidexsys or between Ataportsys and Pciidex.sys. In this race condition, the following conditions are true:
Atapi.sys and Ataport.sys use the stm method to select a transfer mode on a channel. The stm method is in the advanced configuration and power Interface bios. pciidex.sys verifies whether that channel exists by checking for the ide decode enable bit.
If the bios implementation of the stm method has cleared the ide decode enable bit, pciidex.sys determines that the channel does not exist. When this behavior occurs, pciidexsys does not enumerate the channel.
vista troubleshooting guide for this error
Because atapisys and ataportsys never run the stm method as long as there is i o on the channel, the stm method does not have to clear the ide decode enable bit. Therefore, BIOS manufacturers should not clear the ide decode enable bit in the stm method.
Path maximum transmission unit black hole router detection.The following is a list of black hole router detection changes that are included in windows server 2003 sp2.
By default, black hole detection is turned on.
Black hole probing is performed only for connections in established or advanced states.
Black hole probing is performed only for connections on which there is no full-size segment acknowledgement.
If black hole probing fails, the tcp maximum segment size of the connection is restored to what it used to be before probing.
• With black hole router detection turned off in versions of Windows that are earlier than windows server 2003 sp2, a connection times out approximately after 63 rtt. In windows server 2003 sp2, connections time out after 71 * rtt.
Remove Hibernation in Windows Vista troubleshooting
Hibernation is not made unavailable when you set the value of the hibernate after setting to never by using the power options item in windows vista control panel.
To make hibernation unavailable on windows vista, follow these steps:
1. Click start, and then type cmd in the start search box.
2. In the search results list, right-click command prompt, and then click run as administrator.
3. When you are prompted by user account control, click continue.
4. At the command prompt, type powercfg.exe hibernate off, and then press enter.
5. Type exit, and then press enter.
To make hibernation available, follow these steps for vista troubleshooting:
1. Click start on windows vista, and then type cmd in the start search box.
2. In the search results list, right-click command prompt, and then click run as administrator.
3. When you are prompted by user account control, clicks continue.
4. At the command prompt, type powercfg.exe hibernates on, and then press enter.
5. Type exit, and then press enter to close the command prompt window.
I am windows vista admin and I like to share my vista problem troubleshooting knowledge with others.
Article from articlesbase.com
Article from articlesbase.com
This tutorial will take a look at the “Hyper-v Manager” built-in to Windows Server 2008 R2. !! For this to work your computers/servers CPU will have to support hardware assisted “Virtualization” and have it enabled in the BIOS. !!
Related Microsoft Windows Server Guide Articles
Thursday, July 21, 2011
Announcing the Windows Vista and Windows Server 2008 Service Pack 2 Customer Preview Program (CPP) [download os]
In late October I announced the Beta of Service Pack 2 for Windows Vista and Windows Server 2008 - beginning with a small group of Technology Adoption Program customers. This week we're opening up the beta to a broader audience. Starting today, MSDN and TechNet subscribers will have access to the Windows Vista and Windows Server 2008 Service Pack 2 Beta to begin testing.
Beginning Thursday Dec. 4th, we will be making the Windows Vista and Windows Server 2008 Service Pack 2 Beta available to everyone through a Customer Preview Program (CPP). The CPP will launch on TechNet and be available to anyone interested in trying out this service pack. The CPP is intended for technology enthusiasts, developers, and IT Pros who would like to test Service Pack 2 in their environments and with their applications prior to final release. For most customers, our best advice would be to wait until the final release prior to installing this service pack.
For those of you who choose to test this service pack, we encourage you to install the beta as soon as you can; your feedback will help us to ship a solid and stable service pack for Windows Vista.
Windows Vista SP2 builds on the solid foundation of Windows Vista SP1, and represents our ongoing commitment to Windows Vista today. Windows Vista SP2 includes all of the updates that have been delivered since the release of Windows Vista SP1, and incorporates improvements discovered through automated feedback from the Customer Experience Improvement Program (where users voluntarily opt-in to sending Microsoft error reports from their systems). In addition to these updates, SP2 also includes support for new types of hardware and emerging standards that will grow in importance in the coming months. For specific changes in Windows Vista SP2 - see my previous post on Windows Vista SP2 or check out the notable changes document.
Your feedback from testing will help us deliver the highest quality release possible. As of today, we are tracking to ship Windows Vista SP2 in the first half of 2009.
Tags: Windows Vista, Announcement, Developers, IT Pro, Technology Enthusiasts, SP2, Service Pack, Service Pack 2
Beginning Thursday Dec. 4th, we will be making the Windows Vista and Windows Server 2008 Service Pack 2 Beta available to everyone through a Customer Preview Program (CPP). The CPP will launch on TechNet and be available to anyone interested in trying out this service pack. The CPP is intended for technology enthusiasts, developers, and IT Pros who would like to test Service Pack 2 in their environments and with their applications prior to final release. For most customers, our best advice would be to wait until the final release prior to installing this service pack.
For those of you who choose to test this service pack, we encourage you to install the beta as soon as you can; your feedback will help us to ship a solid and stable service pack for Windows Vista.
Windows Vista SP2 builds on the solid foundation of Windows Vista SP1, and represents our ongoing commitment to Windows Vista today. Windows Vista SP2 includes all of the updates that have been delivered since the release of Windows Vista SP1, and incorporates improvements discovered through automated feedback from the Customer Experience Improvement Program (where users voluntarily opt-in to sending Microsoft error reports from their systems). In addition to these updates, SP2 also includes support for new types of hardware and emerging standards that will grow in importance in the coming months. For specific changes in Windows Vista SP2 - see my previous post on Windows Vista SP2 or check out the notable changes document.
Your feedback from testing will help us deliver the highest quality release possible. As of today, we are tracking to ship Windows Vista SP2 in the first half of 2009.
Tags: Windows Vista, Announcement, Developers, IT Pro, Technology Enthusiasts, SP2, Service Pack, Service Pack 2
Windows Vista Service Pack 2 Beta [windows vista]
As you know we are getting ready to talk about Windows 7 at the PDC next week. Before we do that, I thought I would give you an update on our latest work for Windows Vista.
We are committed to continually improving Windows, and we've been getting some questions about the timing of the next service pack for Windows Vista. Following the success of Windows Vista Service Pack 1 last spring, we have been working hard on Windows Vista Service Pack 2. As a part of the development and testing process, we're going to start by providing a small group of Technology Adoption Program customers with Windows Vista SP2 Beta for evaluation next Wednesday, October 29. The final release date for Windows Vista SP2 will be based on quality. So we'll track customer and partner feedback from the beta program before setting a final date for the release.
Windows Vista SP2 Beta contains previously released fixes focused on addressing specific reliability, performance, and compatibility issues. We expect Windows Vista SP2 will retain compatibility with applications that run on Windows Vista and Windows Vista SP1 and are written using public APIs.
Because we've adopted a single serviceability model, these improvements are integrated into a single service pack covering both Windows Vista (client) and Windows Server 2008 (server) versions. This should also minimize deployment and testing complexity for our customers.
In addition to previously released updates since the launch of Windows Vista SP1, Windows Vista SP2 contains changes focused on supporting new types of hardware and adding support for several emerging standards:
I look forward to sharing more about Windows Vista SP2 in the future - stay tuned!
Tags: Windows Vista, Announcement, Featured News, Windows Vista SP1, Windows Vista SP2
We are committed to continually improving Windows, and we've been getting some questions about the timing of the next service pack for Windows Vista. Following the success of Windows Vista Service Pack 1 last spring, we have been working hard on Windows Vista Service Pack 2. As a part of the development and testing process, we're going to start by providing a small group of Technology Adoption Program customers with Windows Vista SP2 Beta for evaluation next Wednesday, October 29. The final release date for Windows Vista SP2 will be based on quality. So we'll track customer and partner feedback from the beta program before setting a final date for the release.
Windows Vista SP2 Beta contains previously released fixes focused on addressing specific reliability, performance, and compatibility issues. We expect Windows Vista SP2 will retain compatibility with applications that run on Windows Vista and Windows Vista SP1 and are written using public APIs.
Because we've adopted a single serviceability model, these improvements are integrated into a single service pack covering both Windows Vista (client) and Windows Server 2008 (server) versions. This should also minimize deployment and testing complexity for our customers.
In addition to previously released updates since the launch of Windows Vista SP1, Windows Vista SP2 contains changes focused on supporting new types of hardware and adding support for several emerging standards:
- Windows Vista SP2 adds Windows Search 4.0 for faster and improved relevancy in searches.
- Windows Vista SP2 contains the Bluetooth 2.1 Feature Pack supporting the most recent specification for Bluetooth Technology.
- Ability to record data on to Blu-Ray media natively in Windows Vista.
- Adds Windows Connect Now (WCN) to simplify Wi-Fi Configuration.
- Windows Vista SP2 enables the exFAT file system to support UTC timestamps, which allows correct file synchronization across time zones.
I look forward to sharing more about Windows Vista SP2 in the future - stay tuned!
Tags: Windows Vista, Announcement, Featured News, Windows Vista SP1, Windows Vista SP2
Why 7? [windows 7]
There's been a lot of lively discussion since I confirmed yesterday that the official name for the next version of the Window client operating system will be "Windows 7" about how we got to the number "7."
I'll say up front, that there are many ways to count the releases of Windows and it's been both a trip down memory lane and quite amusing to read all the different theories about how we got to the number "7."
Anyway, the numbering we used is quite simple. The very first release of Windows was Windows 1.0, the second was Windows 2.0, the third Windows 3.0.
Here's where things get a little more complicated. Following Windows 3.0 was Windows NT which was code versioned as Windows 3.1. Then came Windows 95, which was code versioned as Windows 4.0. Then, Windows 98, 98 SE and Windows Millennium each shipped as 4.0.1998, 4.10.2222, and 4.90.3000, respectively. So we're counting all 9x versions as being 4.0.
Windows 2000 code was 5.0 and then we shipped Windows XP as 5.1, even though it was a major release we didn't' want to change code version numbers to maximize application compatibility.
That brings us to Windows Vista, which is 6.0. So we see Windows 7 as our next logical significant release and 7th in the family of Windows releases.
We learned a lot about using 5.1 for XP and how that helped developers with version checking for API compatibility. We also had the lesson reinforced when we applied the version number in the Windows Vista code as Windows 6.0-- that changing basic version numbers can cause application compatibility issues.
So we decided to ship the Windows 7 code as Windows 6.1 - which is what you will see in the actual version of the product in cmd.exe or computer properties.
There's been some fodder about whether using 6.1 in the code is an indicator of the relevance of Windows 7. It is not.
Windows 7 is a significant and evolutionary advancement of the client operating system. It is in every way a major effort in design, engineering and innovation. The only thing to read into the code versioning is that we are absolutely committed to making sure application compatibility is optimized for our customers.
We're just over a week away from showing off Windows 7 at PDC and WinHEC. I look forward to sharing more soon!
Tags: Featured News, Windows 7
I'll say up front, that there are many ways to count the releases of Windows and it's been both a trip down memory lane and quite amusing to read all the different theories about how we got to the number "7."
Anyway, the numbering we used is quite simple. The very first release of Windows was Windows 1.0, the second was Windows 2.0, the third Windows 3.0.
Here's where things get a little more complicated. Following Windows 3.0 was Windows NT which was code versioned as Windows 3.1. Then came Windows 95, which was code versioned as Windows 4.0. Then, Windows 98, 98 SE and Windows Millennium each shipped as 4.0.1998, 4.10.2222, and 4.90.3000, respectively. So we're counting all 9x versions as being 4.0.
Windows 2000 code was 5.0 and then we shipped Windows XP as 5.1, even though it was a major release we didn't' want to change code version numbers to maximize application compatibility.
That brings us to Windows Vista, which is 6.0. So we see Windows 7 as our next logical significant release and 7th in the family of Windows releases.
We learned a lot about using 5.1 for XP and how that helped developers with version checking for API compatibility. We also had the lesson reinforced when we applied the version number in the Windows Vista code as Windows 6.0-- that changing basic version numbers can cause application compatibility issues.
So we decided to ship the Windows 7 code as Windows 6.1 - which is what you will see in the actual version of the product in cmd.exe or computer properties.
There's been some fodder about whether using 6.1 in the code is an indicator of the relevance of Windows 7. It is not.
Windows 7 is a significant and evolutionary advancement of the client operating system. It is in every way a major effort in design, engineering and innovation. The only thing to read into the code versioning is that we are absolutely committed to making sure application compatibility is optimized for our customers.
We're just over a week away from showing off Windows 7 at PDC and WinHEC. I look forward to sharing more soon!
Tags: Featured News, Windows 7
Windows Vista SP2 RTM + Windows Vista SP1 Blocker Tool Removed [download os]
Today we are announcing the Release to Manufacturing (RTM) of Service Pack 2 (SP2) for Windows Vista and Windows Server 2008. SP2 represents the latest step in Microsoft’s commitment to continuous improvement. It includes all updates that have been delivered since SP1, as well as support for new types of hardware and emerging hardware standards.
As we have mentioned before, here are some of the key benefits of Windows Vista SP2:
Business customers with Windows Vista will find that the transition from Windows Vista to Windows 7 will be significantly more straightforward due to the high degree of compatibility between Windows Vista and Windows 7. If your Windows Vista SP1 deployment is already underway we recommend you continue with SP1 as planned. Then you can deploy SP2 using your systems management infrastructure. If you are in the early stages of deployment or still planning Windows Vista deployment our best advice is that you plan on testing and deploying Windows Vista SP2. For more, I suggest reading this blog post from Gavriella Schuster in regards to guidance on Windows deployments.
We expect Windows Vista and Windows Server 2008 SP2 to be publicly available in Q2 2009.
As a quick reminder, Windows Vista SP1 Service Pack Blocker Tool is being removed today, as we announced back in January. For customers who previously had the blocker tool in place, Windows Vista SP1 will now be offered to them via Windows Update.
Tags: Windows Vista, Announcement, Windows Server 2008, Windows Search 4.0, Windows Vista SP2, Service Pack 2, Service Pack Blocker Tool, exFAT
As we have mentioned before, here are some of the key benefits of Windows Vista SP2:
- Windows Search 4.0 for faster and improved relevancy in searches
- Bluetooth 2.1 Feature Pack supporting the most recent specification for Bluetooth Technology
- Ability to record data on to Blu-Ray media natively in Windows Vista
- Adds Windows Connect Now (WCN) to simplify Wi-Fi Configuration
- Windows Vista SP2 enables the exFAT file system to support UTC timestamps, which allows correct file synchronization across time zones.
Business customers with Windows Vista will find that the transition from Windows Vista to Windows 7 will be significantly more straightforward due to the high degree of compatibility between Windows Vista and Windows 7. If your Windows Vista SP1 deployment is already underway we recommend you continue with SP1 as planned. Then you can deploy SP2 using your systems management infrastructure. If you are in the early stages of deployment or still planning Windows Vista deployment our best advice is that you plan on testing and deploying Windows Vista SP2. For more, I suggest reading this blog post from Gavriella Schuster in regards to guidance on Windows deployments.
We expect Windows Vista and Windows Server 2008 SP2 to be publicly available in Q2 2009.
As a quick reminder, Windows Vista SP1 Service Pack Blocker Tool is being removed today, as we announced back in January. For customers who previously had the blocker tool in place, Windows Vista SP1 will now be offered to them via Windows Update.
Tags: Windows Vista, Announcement, Windows Server 2008, Windows Search 4.0, Windows Vista SP2, Service Pack 2, Service Pack Blocker Tool, exFAT
Subscribe to:
Posts (Atom)