Archive for the 'English' Category

Kaseya Announces Executive Webinar Series to Address Challenges in Strategic IT Management

Published on September 4, 2010 in English, Kaseya and MSP. 0 Comments

LAUSANNE, SWITZERLAND – August 4, 2010 – Kaseya®, the leading global provider of IT systems management software, today announced the Kaseya Innovation Series: Conversations by Executives for Executives. This compelling series of monthly webinars will bring together Fortune 500 CIOs/CTOs and technology industry leaders for informal, neutral conversations on pressing issues in enterprise technology service and support.

Each webinar is designed to approach a single IT issue from a strategic, ROI-based perspective through in-depth discussion, moderated by Anthony Juliano, CTO & general partner, from the New York-based strategic advisory firm Landmark Ventures.

“We’re delighted to offer a platform for forward-thinking executives to share their thoughts and insight with their peers within the IT community,” said Pete Coleman, vice president of enterprise services at Kaseya. “Staying current with the demands of the highest levels of enterprise keeps us on track to tailor our efforts and development for the future.”

These three free webinars offer a valuable perspective on the challenges inherent in strategic IT management:

Hidden Costs of Laptops: Juxtaposing Worker Mobility Mandates with Shrinking IT Budgets

Driven by developing trends in sustainability, technology and social interaction, the traditional service delivery and operational aspects of the enterprise are shifting to predominantly mobile platforms. CIOs now face the unique paradox: how to meet mandates for increased worker mobility while working with reduced IT budgets?

Key Issues:

  • The unspoken costs of mobility
  • Controlling mobile endpoint risk
  • Strategies for retaining budget

General troubleshooting, Internet Explorer

Published on February 28, 2010 in English, Internet Explorer and Windows XP. 1 Comment

General Troubleshooting
This document provides troubleshooting recommendations for issues encountered with Internet Explorer 7 running on Windows XP.
Objectives
● Discuss new Internet Explorer features and functionality.
● Discuss potential user issues with IE7.
● Discuss changes to standard troubleshooting practices on Internet Explorer 7 as compared with Internet Explorer 6.
● Demonstrate techniques for running a safe configuration of IE7 to troubleshoot issues with browser stability or problems with add-ons.

Overview
The following resources provide overview, features and usability information on Internet Explorer 7.
Technology Overview: Microsoft® Windows® Internet Explorer 7
This paper provides a technical overview of Internet Explorer 7.
Objectives:
● Discuss new security features implemented in Internet Explorer 7.
● Discuss the Phishing Filter in IE7 and demonstrate configuration options for this security feature.
● Identify usability and functionality enhancements in Internet Explorer 7.
Reference:
1. Source: Technology Overview: Microsoft® Windows® Internet Explorer 7* 

2. http://www.microsoft.com/downloads/details.aspx? FamilyId=B2AC8F30-2D88-45B6-90AE-ED266161F463&displaylang=en <http://www.microsoft.com/downloads/details.aspx?FamilyId=B2AC8F30-2D88-45B6-90AE-ED266161F463&displaylang=en>  

* © Microsoft Corporation / Updated January 2006 for Beta 2 
Key Points
This document covers the changes in Internet Explorer 7, including the following, which are the most significant for home users:
● Security and privacy features such as warnings when non-default security settings are in use, and the Phishing Filter
● New usability changes such as tabbed browsing, printing changes, RSS feeds
Internet Explorer 7 Release Notes
The release notes for Internet Explorer 7 describe known issues related to the browser.
Objectives:
● Discuss application compatibility issues identified in the release notes.
● Discuss other potential support issues identified in the release notes.
Reference:
3. Source: Release Notes for Internet Explorer 7 Beta 2 Preview* 

4. <http://msdn.microsoft.com/ie/releasenotes/default.aspx>  

* © Microsoft Corporation / Updated January 2006 for Beta 2 
Key Points
Phishing Filter in the Internet Explorer 7 Help
The help documentation accompanying Internet Explorer 7 provides overview and how-to information on Internet Explorer features and functionality. The help content related to the new Phishing Filter is particularly helpful in understanding how this security feature should be used.
Objectives:
● Discuss the Phishing Filter Frequently Asked Questions.
Reference:
5. Source: Microsoft Internet Explorer 7 Help* 

6. From the Contents select: 7. Phishing, Viruses and other Internet Threats 8. > Phishing Filter: frequently asked questions 

* Microsoft Internet Explorer Help 
Key Points
The Phishing Filter in Internet Explorer helps protect you against phishing threats by analyzing web sites and warning you when a site has some characteristics of a phishing site. The filter is also updated to protect against sites that have been reported to be malicious.
Troubleshooting Tools
This section provides information on several new features of Internet Explorer 7 that can be used while troubleshooting user issues.
Delete Browsing History
The Delete Browsing History option provides a single point of access to clear all of the user data types saved by Internet Explorer by default. You can access the Delete Browsing History interface from the Tools menu in Internet Explorer, or by pressing Delete in the Internet Options interface.
Use the Delete Browsing History while troubleshooting a user issue to resolve issues that could be caused by corrupt or damaged data files that are used by Internet Explorer.
Note: You should inform your user that saved passwords and cookies will be deleted. Cookies are used by many web sites to store site identity and passwords. If the user needs to save some of this information you should offer assistance exporting Cookies and provide a caution that locally saved passwords will be cleared.
Internet Explorer No Add-ons Mode
Internet Explorer No Add-ons Mode provides an Internet Explorer process environment free of ActiveX controls, Browser Helper Objects and other third party code that could contribute to issues with the browser. Use this mode with a user to determine if a problem is being caused by code loading in the Internet Explorer process.
If the issue not present when running in No Add-ons mode you can use the Manage Add-ons interface to isolate the specific add-on components that are contributing to the issue. To do this:
1. Open Manage Add-ons.
2. Set the Show setting to “Add-ons that have been used by Internet Explorer”.
3. Disable half of the components listed here, then start Internet Explorer normally and check for the issue.
a. If the issue is still present, re-enable the components currently disabled, and then disable the other half. The problem should be present after this test.
b. If the issue is no longer present, re-enable small sets of components, testing for the issue after each set until you determine the add-on or add-ons that are causing the issue.
c. Note the name and file of the isolated component. If it is an ActiveX control, use the Delete ActiveX option in the Manage Add-ons interface to remove it.
d. If the component is not ActiveX, search for and rename the file in Windows Explorer.
Reset all Defaults
One of the most significant new features of Internet Explorer 7 that impacts support and troubleshooting is the Reset all Defaults option on the Advanced tab of Internet Options. Understanding the impact of this tool before using it on a support call is very important to ensure that you can make your user aware of the consequences.
Significant issues encountered with versions of Internet Explorer often resulted in the need for replacing files, re-registering DLLs, and disable ActiveX Controls, toolbars and other Browser Helper Objects. Reset all Defaults in Internet Explorer 7 provides an automated method of performing these actions.
The Reset all Defaults tool performs the following steps:
● Clear user data:
○ History
○ Temporary Internet Files
○ Web form information
○ Saved passwords
○ Typed URL history in the Address bar
○ Run Most Recently Used (MRU) addresses and commands
○ Cookies.
● Reset user configuration options such as the Home Page, Privacy configuration.
● Reset Security configuration to defaults.
● Disable all 3rd party ActiveX controls, toolbars and Browser Helper Objects
● OEM/IEAK settings restored from the branding.cab file, if it exists
● Removes and Rebuilds the following registry keys:
○ HKCU\Software\Microsoft\Internet Explorer
○ HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings
● Resets all settings for Internet Explorer to the default settings per the inetcpl.cpl

Potential Issues and Troubleshooting
Potential user issues with Internet Explorer 7 could relate to issues displaying web pages, problems running Internet Explorer, or issues with new features, such as RSS feeds. Issues in these and other categories are addressed in the sections that follow.
Internet Explorer 7 not Recognized by Some Web Sites
This issue could appear as many error messages, depending on how particular web sites report the problem.
Cause
Web sites often check the web browser product name and version to determine if your browser is compatible with their web site, or to provide a certain experience on the site. Some sites support only a limited set of browsers and versions, and in those cases Internet Explorer 7 may not be in the supported list. You may be unable to browse to the site with this version.
Note: This is very common with bank web sites and other sites that provide access to very sensitive information. To ensure best compatibility and confidentiality they may restrict logon to their web applications from unsupported web browsers.
More Information
The browser reports its version information using a value called the “User Agent String”. Internet Explorer sends the following User Agent String to a web site it is accessing:
Mozilla/4.0 (compatible; MSIE 7.0b; Windows NT 6.0)
Web administrators and developers must either not perform user agent string-based validation, or update their validation to permit access to their site by Internet Explorer 7.
Resolution
Considerations for resolving this issue are as follows:
● If you encounter such an access issue, it is generally recommended that you contact the web administrator or support for the web application to determine the best course of action.
● If you encounter the issue while running a pre-release or Beta version of Internet Explorer, the web administrator may be unable to support the browser version you are using.
● If the problem cannot be resolved you can modify the version Internet Explorer reports to web sites in the User Agent String, but doing so can cause problems or errors in the communication with web sites. You make this change at your own risk.
Changing the User Agent String
If you need to change the user agent string that Internet Explorer 7 reports, you can modify the following registry values:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent
“Version”=”MSIE 6.0″
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\User Agent\Post Platform
“SV1″=”"
HKLM\SOFTWARE\Microsoft\Internet Explorer\Version Vector
“IE”=”6.0000″
Important: You should caution your user that they must make this change at their own risk. In making this change they face potential issues and errors when accessing sites not written for or tested with the browser version they are using.
Issue with IE7 Beta that does not occur in IE6
In situations where a feature or component of Internet Explorer, or a particular web site does not function the same on Internet Explorer 7 Beta as it did on Internet Explorer 6, it is important to evaluate the issue and communicate it as a potential problem to your Microsoft contacts.
1. Evaluate the issue a user reports by testing it on another computer with Internet Explorer 6 installed.
a. Does IE6 behave the same as IE7?
b. If you encounter the same behavior on IE6 as the user sees on IE7, it is not a new issue, and thus does not need to be reported as part of the Beta.
2. If IE7 behaves differently than IE6:
a. Is the issue with a web site?  If so, communicate the URL of the problem page to your Microsoft contact. If the page cannot be reached directly, provide the site URL, and specific steps to generate the problem.
b. Is the issue with an Internet Explorer feature or component? If so, write a description of the steps to reproduce the problem and communicate that information to your Microsoft contact.
Internet Explorer Cannot Display the Webpage
This section describes the troubleshooting for problems displaying web pages. The new information page displayed when this problem occurs contains the text:
Internet Explorer cannot display the webpage
Troubleshooting for these issues is similar to the troubleshooting for a Page Cannot be Displayed issue in Internet Explorer 6.
Cause
Potential causes of this issue are the same as those outlined in the following Microsoft Knowledge Base article:
Error message when you try to access a Web site in Internet Explorer: “Page Cannot Be Displayed” (326155)
From the article:

9. The problem may occur for many reasons. These reasons include, but are not limited to, the following:  ● Connectivity issues or network-related issues, including the following: ○ A conflict with the firewall or a firewall configuration issue  ○ Issues with network drivers  ○ Issues with winsock or TCP/IP  ○ Erroneous entries in the Hosts file  ● Third-party party software or Internet connections settings issues, including the following: Issues with the Startup files or other potential service conflicts  ○ User Account corruption  ○ Malicious software has been installed  ● Internet Explorer configuration settings, including the following:  ○ Internet Explorer is not optimized  ○ Internet Explorer has conflicting or inappropriate settings  ○ Conflicts with third-party party browser extensions  ○ Problems with DLL files or use of unregistered DLL files  ● Damaged of missing core Windows files 

Resolution
Troubleshooting these issues with Internet Explorer 7 installed is made easier due to the presence of the Internet Explorer (No Add-ons) mode, the new Delete Browsing History option, and the Reset all Defaults recovery feature. Following the process recommended by the article referenced above, you can use the troubleshooting as follows:
● Where to start
○ Test other known good sites
○ Verify connectivity
○ Run the Network Diagnostics Tool
■ If you do not receive errors related to the IP Address and DNS Server, it is likely that your connectivity is functional. Skip to Section 2.
■ Otherwise, use Section 1 steps in the article to troubleshoot connectivity or other network issues.
1. Section 1: Connectivity issues or network-related issues
This troubleshooting remains unchanged from what is recommended for Windows XP with Internet Explorer 6.
2. Section 2: Third-party software or Internet connections settings issues
Troubleshooting in this area benefits from the Delete Browsing History and the No Add-ons mode of Internet Explorer 7.
a. To start this troubleshooting, use the Delete Browsing History option in the Tools menu. This clears the Temporary Internet Files, History and saved forms data.
b. The new first recommended step for this section is to test in Internet Explorer (No Add-ins) mode. You can start this from Start, All Programs, Accessories, System Tools, Internet Explorer (No Add-ins).
i. If this mode resolves the issue, use Manage Add-ons to isolate the browser add-on or add-ons that are contributing to the problem.
ii. If this mode does not resolve the issue, continue troubleshooting with the following steps.
c. Part 1: Test in Safe mode with Networking
d. Part 2: Clean boot Windows XP
e. Part 3: Test by using a new user account
f. Part 4: Run antivirus software and antispyware software
3. Section 3: Internet Explorer configuration settings
Troubleshooting in this area benefits from the Reset all Defaults option in Internet Explorer 7.
a. The new troubleshooting step recommended for this section is the use of the Reset all Defaults option on the Advanced tab of Internet Options.
This is a new resolution step that performs all remaining tasks previously recommended in this section.
Important: After performing a Reset all Defaults in Internet Explorer 7, all browser add-ons are set to Disabled in Manage Add-ons. This ensures that previously installed add-ons will not be running after the reset, but will also mean that desirable components will need to be re-enabled. Reinstalling a browser add-on will not typically re-enable it in this interface, so it will not be functional until that step is taken manually. 
Note: Re-registering Internet Explorer files should not be needed on Internet Explorer 7. The Reset all Defaults action takes the place of this as a troubleshooting step. In the event of more catastrophic problems that the reset does not resolve you can also uninstall and then reinstall Internet Explorer 7 on Windows XP to ensure that it is properly installed.
4. Section 4: Damaged or missing core Windows files
This troubleshooting remains unchanged from what is recommended for Windows XP with Internet Explorer 6.
a. Part 1: Run System File Checker
b. Part 2: System Restore
Internet Explorer Terminates Unexpectedly or does not Start
This issue category deals with problems in which the Internet Explorer process is terminating or not starting properly.
Cause
There is a possibility for user issues related to stability problems that result from problem add-ins, damaged files, problem configuration or corruption. Unlike previous browser versions
Resolution
To troubleshoot browser stability issues, use the following steps:
1. Test with Internet Explorer starting on a blank home page.
a. Click Start, Run and then using the following command:
iexplore about:blank
b. If Internet Explorer starts without a problem, go to Internet Options and verify the home page. Note the current setting and then click Use blank to set the default to “about:blank”. Test by opening the browser normally.
2. Use the Delete Browsing History option in the Tools menu and test again. This clears the Temporary Internet Files, History and saved forms data.
3. If a blank home page does not resolve the issue, try starting Internet Explorer in No Add-ins mode.
a. Go to Start, All Programs, Accessories, System Tools, and then click Internet Explorer (No Add-ins).
b. If the problem is not present in this mode, use Manage Add-ons to isolate the specific add-on or add-ons.
c. If the problem is still present, continue with the remaining troubleshooting.
4. Test while logged on as an alternate user. This will help isolate problems specific to one user account or user profile.
5. The next new troubleshooting step recommended for this section is the use of the Reset all Defaults option on the Advanced tab of Internet Options.
This is a new resolution step that performs all remaining tasks previously recommended in this section.
Phishing Filter Issues
The Phishing Filter in Internet Explorer 7 has the potential to generate user questions, particularly around the reporting mechanisms for phishing sites, as well as the methods for following up when a user’s site is identified as a reported phishing site.
Site Misidentified as Suspicious or as a Reported Phishing Site
In the event that a known trustworthy site is identified as suspicious, you can use the Report this Website feature to identify to Microsoft that the site is not a phishing risk. These reports are used to identify categorization issues.
Report a Phishing Site
If you are on a website that you suspect is a phish, you can report it to Microsoft. This helps protect the rest of the Internet Explorer user base from the phishing attempt.
To report a site to Microsoft, use the Report This Website option in the Tools, Phishing Filter menu in Internet Explorer.
RSS Feed Issues
Import and Export Feeds
In the event that you need to migrate feeds from one user account or machine to another you can use the File, Import and Export option in Internet Explorer.
Exported feeds for a user are saved as a single feeds.opml file, by default in the user’s My Documents folder.
An example exported feeds.opml file showing one entry will be in a format as follows:
<opml version=”1.1″><head><title>Feeds</title></head><body><outline text=”Internet Explorer Team Blog” xmlUrl=”http://go.microsoft.com/fwlink/?LinkId=58643” type=”rss”/></body></opml>
Additional entries would be included in this file as separate <outline> tags in the same format as the Internet Explorer Team Blog entry shown above.
This is an Outline Processor Markup Language (OPML) file, which is defined in the OPML specification available from <http://www.opml.org/>.
Feed Not Updating
Cause
This problem could result from connectivity issues with the feed server, a frequency in the properties for the feed that is too long, or a problem with the local feed cache.
Resolution
To resolve an issue with a feed not updating, perform the following steps:
1. First, check the feed on the host site to ensure that the server side feed is updating properly.
2. Check the properties of the feed in Internet Explorer and verify that the desired update frequency is set.
3. If the issue is not related to the frequency, manually refresh the feed to see if the contents change.
4. If you still encounter problems with the feed, export all feeds on the machine, use the “Feeds not Listed or Cannot Subscribe to Feed” troubleshooting in the section below.
Feeds Not Listed or Cannot Subscribe to Feed
Cause
Problems subscribing to new feeds, or an incomplete feeds list could result from corruption in the feed storage, user profile issues, or issues related to browser add-ons.
Resolution
To resolve issues with missing feeds, or problems subscribing to new feeds perform the following steps:
1. Add a feed from an alternate, known-working site, such as:
<http://www.microsoft.com/windows/rss>
2. Logon as different user and test.
3. Test in Internet Explorer No Add-ins mode. If the problem is resolved in this mode, use Manage Add-ons to isolate the specific browser add-ons that are contributing to the issue.
4. If the problem continues in Internet Explorer No Add-ons mode, clear the feeds and re-import using the following steps:
a. Export the feeds on the machine.
b. Delete all feeds by closing Internet Explorer and deleting the files in %userprofile%\Local Settings\Application Data\Microsoft\Feeds.
c. Open Internet Explorer and add one feed for a known-working site, such as:
<http://www.microsoft.com/windows/rss>
d. After verifying that the known-working feed is working, import the previously subscribed feeds.

How to repair Internet Explorer

Published on February 28, 2010 in English, Internet Explorer, Tweaks, Uncategorized, Windows 7, Windows 98/ME, Windows Vista and Windows XP. 0 Comments

To repair Internet Explorer
1. Upgrade the Internet Explorer to the latest version. To install the latest version of Interne t Explorer visit the following Web site:  http://www.microsoft.com/windows/ie/default.mspx  

2. Repair or reinstall Internet Explorer. 
• Windows Vista  Note Since Windows Vista is pre loaded with Internet Explorer 7 there is no direct way to Uninstall the Internet Explorer.
However there are few ways to repair Internet explorer 7 that could address the issue. 
To Repair Internet explorer 7 in Windows Vista try following options: 
• Disable all add-ons 
1. Click to open Internet Explorer.  
2. On the Tools menu, point to Manage Add-ons, and then click Enable or Disable Add-ons.    
• Reset Internet Explorer to default settings  
If disabling add-ons does not solve the problem, try resetting Internet Explorer back to its default settings.
This removes all changes that have been made to Internet Explorer since it was installed.
But it does not delete your favorites or feeds. 
1. Close all Internet Explorer or Windows Explorer windows.  
2. Click to open Internet Explorer.  
3. Click the Tools button, and then click Internet Options.  
4. On the Advanced tab, click Reset.  
5. Click Reset.  
6. When you have finished, click Close, and then click OK.  
7. Close Internet Explorer and reopen it for the changes to take effect

 

• Run the Microsoft Malicious Software Removal Tool 
Note Malicious software and viruses can frequently cause Internet Explorer to slow down or stop working. 
If you can access the Internet, use the Malicious Software Removal Tool to check the computer for viruses and malicious software.
Click the following link for more help: 
http://www.microsoft.com/security/malwareremove/default.mspx

 • Update Internet Explorer  
Running Windows Update can frequently correct problems by replacing out-of-date files and fixing vulnerabilities. 
1. Click to open Internet Explorer.  
2. On the Tools menu, click Windows Update.  
3. Follow instructions on the Windows Update page.  
Note If you cannot open Internet Explorer or if it opens briefly and then closes, the problem might be caused by low memory, or corrupted or missing system files.
Restart the computer to clear the memory and then open Internet Explorer by itself.    

• Microsoft Windows XP 
Note You must use Internet Explorer 6 with Windows XP.
You cannot use an earlier version of Internet Explorer with Windows XP. 
a.  To Install or reinstall Internet Explorer 6 follow the following steps:  Note Internet Explorer 6 Service Pack 2 is the last version of Internet Explorer 6.
If the computer is already running Internet Explorer 6 Service Pack 2, you must reinstall the service pack to repair the original installation. 
• Visit http://www.microsoft.com/windows/ie/downloads/critical/ie6sp1/default.mspx, and then click Internet Explorer 6 Service Pack 1 under Download, and then click Download.
 Or 
• Execute the Internet Explorer.inf file from \Windows \Inf folder 
1. Click Start, Click Search, select All files and folders.  
2. Make sure that Search system folders and Search subfolders are also checked.  
3. In the All or part of the file name box, type ie.inf .  
4. In the Look in drop-down menu, select C: or the letter of the hard disk that contains the Windows folder and then click Search button.  
5. In the search results pane, find the ie.inf file that is located in Windows\Inf folder.  
6. Right-click the ie.inf file and then click Install on the context menu.  
7. Insert Windows XP CD when it is requested.  
8. Restart the computer when the file copy process is complete.     

 

 

• Windows XP with Internet Explorer 7  
To uninstall Internet Explorer 7 to return to Internet Explorer 6 on Windows XP 
1. Click Start and then click Control Panel.  
2. Click Add or Remove Programs.  
3. Check Show updates at the top of the dialog box.  
4. Scroll down the list and highlight the version of Internet Explorer 7 that you are running, and then click Change/Remove.  Note If you are running Internet Explorer 7 Beta 2 Preview – March 20 or later, you do not have to check Show updates.  
5. Go here and select the appropriate version of Internet Explorer 7 for the operating system.    
Note If you receive one of the following error messages when you try to install Internet Explorer Service Pack 1, go to step 2:  Setup has detected a newer version of Internet Explorer already installed on this system.  Setup cannot continue  

b.  Install updates to the Windows operating system. 

• To reinstall updates to the Windows operating system, visit <http://windowsupdate.microsoft.com>, and then click Scan for updates. If there are updates to install, click Install Now.
• Microsoft Windows 98, Windows 98 Second Edition, Windows Millennium Edition, and Windows 2000 

a.  Repair Internet Explorer. 

1. Click Start, click Settings, and then click Control Panel.  
2. Double-click Add/Remove Programs.  
3. Click the version of Internet Explorer that appears in the list of installed software. If no version of Internet Explorer appears, go to step b.  
4. Click Add/Remove.  
5. Click Repair Internet Explorer, and then click OK.  
6. When you are prompted to repair Internet Explorer, click Yes.  
7. Restart the computer.    

b.  If repairing Internet Explorer did not resolve the issue, install Internet Explorer 6 Service Pack 1 from the Internet Explorer Web site or install Internet Explorer 6 from your MSN CD.  Note If the computer is already running Internet Explorer 6 Service Pack 1, you must reinstall the service pack to repair the original installation. 

• To install Internet Explorer 6 Service Pack 1, visit http://www.microsoft.com/windows/ie/downloads/critical/ie6sp1/default.mspx, click Internet Explorer 6 Service Pack 1 under Download, and then click Download.
• To install Internet Explorer 6 from your MSN CD, view one of the following articles. For additional information about how to install Internet Explorer 6 from the MSN CD, click the following article numbers to view the articles in the Microsoft Knowledge Base: 

815692  <http://support.microsoft.com/default.aspx?scid=kb;%5bLN%5d;815692>
MSN: How to install Internet Explorer 6.0 from the MSN 8 CD

834336  <http://support.microsoft.com/default.aspx?scid=kb;%5bLN%5d;834336>
MSN: How to install Internet Explorer 6.0 on a Windows 2000-based computer from the MSN Premium or the MSN Plus CD

883084  <http://support.microsoft.com/default.aspx?scid=kb;%5bLN%5d;883084>
MSN: How to install Internet Explorer 6.0 from an MSN version 9.0 CD

Note If you receive one of the following error messages when you try to install Internet Explorer, go to step 2:  Setup has detected a newer version of Internet Explorer already installed on this system.  Setup cannot continue  

c.  Install all updates to the Windows operating system. 
• To install updates to the Windows operating system, visit <http://windowsupdate.microsoft.com>, and then click Scan for updates. If there are updates to install, click Install Now.

 

4. (Windows XP only): Run the Windows File Protection program to repair the Windows installation.  Note This step may require the Windows XP or Windows XP Service Pack 1 installation CD.

a.  Sign in to the computer by using an administrator account.  
b.  Run the System File Checker tool to scan the protected files on the computer. 
a.  Click Start, click Run, type sfc /scannow , and then click OK.  

   
5. Edit the Registry and Install Internet Explorer 6. 

1. Sign in to your computer with an administrator account.  
2. Click Start, and then click Run.  
3. Type regedit, and then click OK.  
4. For each of the following registry keys, right-click the IsInstalled value in the right pane of the Registry Editor window, click Modify, change the Value data to 0 , and then click OK. 
• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{89820200-ECBD-11cf-8B85-00AA005B4383}  
• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{44BBA840-CC51-11CF-AAFA-00AA00B6015C}    
5. Close Registry Editor.  
6. Install Internet Explorer 6 Service Pack 1. 
• Visit http://www.microsoft.com/windows/ie/downloads/critical/ie6sp1/default.mspx, click Internet Explorer 6 Service Pack 1 under Download, and then click Download.
7. Visit http://windowsupdate.microsoft.com, and then click Scan for updates.

Steps for Troubleshooting Slow Network Issues

Published on February 11, 2010 in English, Network and Tweaks. 0 Comments

The following are a few steps which are useful to follow while troubleshooting slow
network communications over a WAN link.

**To troubleshoot network issues more effectively you must know the Ins-and-Outs of
the TCP/IP stack.  For a great beginning (and in depth information) please refer to
the book “Windows Server 2003 TCP/IP Protocols and Services Technical
Reference”.**

1) Take traces simultaneously between client and server

2) Check for delays in these queries
a) QUERY_PATH_INFO
b) QUERY_FS_INFO
c) FIND_FIRST2
d) NT_CREATE_ANDX
e) Trans2 GET_DFS_REFERRAL, NEGOTIATE, SESSION_SETUP_ANDX, LOGOFF_ANDX

        Note : If you are using Network Monitor, you can see the delays better if
you use the following filter:
SMB:Command == 0xA0 ( NT transact )
    Use this filter in combination with the following display options:
Time: (x) Seconds from previous frame
             You can identify the corresponding requests and answers by looking at
the following SMB frame attribute:
SMB: Multiplex ID (MID)

Average Response time from server should be like .002 ms.  If you see a server-side
delay from the client and a client-side delay from the server, then it’s probably a
network issue of some sort.

3) Try sending files to and from different servers and clients on the same segment.
 Try also sending file from server seeing the issue to a different receiving
client.  This may narrow it down to a specific machine seeing the issue.

4) Update all the NIC drivers on client and the server.
5) Set Network card and switch to a 100mb full instead of autodetect  (it is very
important that the two must match.  If they are mismatched then you could see
multiple problems)

6) If possible, start the machine in safe mode with networking and test.  Sometimes
third party components may cause delays.  In cases such as antivirus possibly
causing the slowness (very typical as it sometimes tries to scan everything leaving
and entering the machine) the only true way to test is to fully uninstall the
product because of the Kernel level filter drivers. (Also confirm for any 3rd party
servers such as SAN, SOLARIS, IBM etc.)

7) Try to access share on itself by giving loopback address to the server / client 
which will eliminate network components and take a trace should be done prior to
updating MRXSMB and Redirector

8) Update MRXSMB.sys file and RDBYSS.sys file both on the server side and the
client side  and also netbt.sys file.  Updating the Netbt.sys file will Improve
Redirector / server connections ( solution for Nagling and TCP delayed
acknowledgment ) Here are some articles for each that will help you in updating:

- Latest MRXSMB.sys file for Windows Servers (All Versions)
a) Windows 2003 Server – KB article 913835
b) Windows 2000 Server -  KB article 907546
c) Windows XP SP2 ( All versions) – KB article 896427

      – Latest RDBYSS.sys file for Windows Servers ( All versions)
a) Windows 2003 Server – KB896427
b) Windows 2000 Server – KB907546
c) Windows XP SP2 ( All versions) – KB 903891

      – Latest NetBt.sys file for windows Servers ( All versions)
a) Windows 2000 Server – KB article 984250

* Please check the KB for more updated fixes.  These are just pointers to help
out.
9) A common issue in networking is to mistake a shell issue with a slow network
issue. These issues can be seen in Mapped drives and browsing.  Any time you are
using the GUI you are using shell32.dll.   This would be considered a Performance
based issue. To test this theory you can go to a command prompt and do a Net View
then a Dir of the network resource. Does it populate all information quickly? If so
it may be a shell issue.  Prior to bringing in performance you can try updating the
shell32.dll.  Here are some articles for each that will help you in updating:

- Latest Shell32.dll file for Windows Servers (All Versions)
a) Windows 2003 Server – KB article 903154
b) Windows 2000 Server -  KB article 898068
c) Windows XP SP2 ( All versions) – KB article 912680

* Please check the KB for more updated fixes.  These are just pointers to help
out.

10) TCP Checksum Offloading : The TCP checksum is added to the packet by the
network interface,  not by  the OS’s TCP/IP stack; when capturing on an interface,
packets being sent by the host on which you ‘re capturing are directly handed to
the capture interface by the OS, which means that they are handed to the capture
interface with out a TCP checksum being added to them; So one way to prevent this
from happening is to disable TCP checksum offloading.

Disable TCP / IP checksum offloading. Please follow the procedure to disable the
TCP / IP checksum Offloading
     
a). Click Start, click Run, type ncpa.cpl , and then click OK.  
b). Right-click your network adapter, and then click Properties.  
c) Click the General tab, and then click Configure.  
d) Click the Advanced tab.  
e) In the Property box, click any one of the following properties.   Note We
recommend that you start with the Offload TCP Segmentation property. The problem is
probably caused by the Offload TCP Segmentation property because full support for
this feature is not implemented in the Vpcnets2.sys driver.  • Offload TCP
Segmentation   • Offload Receive IP Checksum   • Offload Receive TCP Checksum   •
Offload Transmit IP Checksum   • Offload Transmit TCP Checksum       
f). In the Value list, click Off, and then click OK.  
g). Test to see if the performance issue has been resolved. If the problem still
occurs, re-enable the property that you turned off, and then disable a different
task offload property. Test if performance has improved after you disable each
property.  

If your NDIS driver does not have the settings available to disable tcp checksum
offloading, then you can disable it by editing the registry as follows

a) Click Start, click Run, type regedit, and then click OK.
b) Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
<http://wiki.colinux.org/cgi-bin/CurrentControlSet>\Services\Tcpip\Parameters
c) Click Edit, point to New, and then click DWORD Value.
d) Type DisableTaskOffload <http://wiki.colinux.org/cgi-bin/DisableTaskOffload> as
the entry name, and then press ENTER.
e) Right-click DisableTaskOffload
<http://wiki.colinux.org/cgi-bin/DisableTaskOffload>, and then click Modify.
f) In the Value data box, type a value of 1, and then click OK.
g) Quit Registry Editor.
h) Restart your computer

11) Use TCPDELACKTICKS if you see that server is not sending any packets nor it is
not responding for more than 200ms , at that point you see TCP ACK packet sent to
resume connection and this behaviour is because of TCP Delayed Ack.  We can edit
TCPDelAckTicks registry value for better performance , use the following registry
key
       
a).  Start Registry Editor (Regedt32.exe). 
b).        Locate and click the following key in the registry, where Adapter GUID
is the globally unique identifier (GUID) for the network adapter that connects to
the clients: 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\Ada
pter GUID  
 On the Edit menu, click Add Value, and then add the following registry value: 
Value name: TcpDelAckTicks Data type: REG_DWORD Value data: You can set this value
to a range from 0 to 6. The default setting is 2 (200 milliseconds).  
 Quit Registry Editor. 
 Restart Windows for this change to take effect.  
This registry value specifies the number of 100-millisecond intervals to use for
the delayed ACK timer on a per-interface basis. By default, the delayed ACK timer
value is 200 milliseconds. If you set the TcpDelAckTicks value to 0, delayed
acknowledgments are disabled. This setting causes the computer to immediately send
an ACK packet for every packet it receives.

 
12) You can also try using TCPAckFrequency registry key.  This will cause every
packet to get Acknowledged, you can reference more information on this by looking
at KB article 328890 or by reading the TCP/IP Protocols and Services Technical
Reference. Understand that this will also cause an increase in data on the lines as
you are acknowledging every packet.  After following 328890, if you don’t see any
changes please look at KB article 815230.  It updates TCPIP.sys.
      
13) Enabling ReadAhead feature on Sequential Reads ( This is very important and
probably a best resource ). Please go through 328237 KB article number. And look
for
        
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanWorkStation\Parameters
             Value name: ReadAheadGranularity
                         Data type: REG_DWORD
      
                       
14) Opportunistic Locking :   By default, opportunistic locking is enabled for
server message block (SMB) clients that run one of the Windows operating systems.
Opportunistic locking allows clients to lock files and locally cache information
without the risk of another user changing the file. This increases performance for
many file operations but may decrease performance in other operations because the
server that grants the opportunistic lock must manage the breaking of that lock
when another user requests access to the file. A network trace is going to be the
determining factor in this.  You will see 8 – 16 second delays in which it is
trying to undo the opportunistic lock.  It may try multiple times.  With that being
the case you can go through the following article to disable Opportunistic
locking:
                       
      <http://vkbinternal/VKBWebService/ViewContent.aspx?scid=KB;EN-US;296264>

15) Check for SMB signing between both client and server.

a) To check for SMB signing Please go to the following registry key
b) Locate, and then click the enablesecuritysignature value under the following key
in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanserver\Parameters
c) To disable SMB signing Please refer to KB article 321733

             
16) The following KB article is one of the useful article I have found that goes
over Network Shares opening slowly, read only or if you get an error message while
trying to open:
<http://vkbinternal/VKBWebService/ViewContent.aspx?scid=KB;EN-US;814112>

17)  Windows 2000 and Windows 2003 server uses Large File Support and not all
earlier version   of OS have this capability to perform faster Write and Read file
operations
So our main goal is to send large Read&X and Write&X , so we can tweak the
performance using SizReqBuf Registry key on Windows NT server . And the main reason
is
Windows NT server works in Raw SMB mode so Windows NT server doesn’t have Large
File Write Support.
To work around this performance issue, make the following registry change on the
Windows NT 4.0-based server:
      a).  Start Registry Editor (Regedt32.exe). 
      b). Locate and click the following key in the registry: 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters  
 On the Edit menu, click Add Value, and then add the following registry value: 
Value Name: SizReqBuf Data Type: DWORD Value Radix: Decimal Value: 65535  
     c)   Quit Registry Editor. 
     e). Restart the server 
After you make this change, the performance of the write process is approximately
the same as a read operation between the two computers.                            
                                              

Note that the SizReqBuf value controls the buffer size for CORE SMB requests.
Setting it to 64 KB has approximately the same effect as Large Write support, which
uses 60-KB buffers.
From the tests completed , please set the ReadAheadGranularity to 16 on the
clients.

Missing swflash.ocx

Published on February 11, 2010 in English, Internet Explorer, Tweaks, Windows 7, Windows 98/ME and Windows XP. 0 Comments

Here is help to all who have a message with missing swflash.ocx. First go to your c:\ drive in my computer, then to windows folder, then search the windows folder for swflash.ocx, you will find it is uninstalled. When your computer find the old file, just simply copy the file by right click on the file, then select copy, now go to C:\WINDOWS\system32\Macromed\Flash and paste it in this folder

Error 1722: “There is a problem with this Windows Installer package . . . ”

Published on February 9, 2010 in English, Windows 98/ME, Windows Vista and Windows XP. 1 Comment

Situation:
While installing Norton Internet Security (NIS) 2004, you see the error message: Error 1722: “There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.”

Solution:
This problem results from trying to install from a corrupted MSI file, from a corrupted copy of the Microsoft Installer. To correct the problem, follow these procedures in order given.

To delete all temporary files
Click Start > Programs > Accessories > Windows Explorer, or double-click the My Computer icon on the desktop.
Click anywhere in the Address bar to select it. (If you do not see the Address bar, then right-click the blank area to the right of Help. On the menu that appears, click Address bar.)
Type this and then press Enter: %temp%

 
The Temp folder for the currently logged-on user displays.
In most cases, you can safely delete the contents. If you are not sure, then copy any files or folders to a different location. To delete the contents, click the Edit menu, and then click Select All.
Press Delete, and then click Yes if prompted to confirm.
Restart the computer.
Try the install process again. If you continue to get the 1722 error, continue on to the next section.

To manually remove corrupt MSI files
Open Windows Explorer.
In Windows 98/ME: click View > Folder Options
In Windows 2000/XP: click Tools > Options or Folder options
· Click the View tab,
In the Advanced Settings pane, under Files and Folders, verify that “Hide file extensions for known file types” is unchecked.
In Windows 95/NT, click “Show all files.”
In Windows 98, in the Advanced settings dialog box, click “Show all files” under the “Hidden files” folder.
In Windows Me/2000/XP, uncheck “Hide protected operating system files” and click “Show hidden files and folders” under the “Hidden files” folder.
· Click Apply > “Like Current Folder” or “Apply to all folders” > OK.
Browse to the Installer folder. In this folder is a number of files with the “.msi” extension.
In Windows 98/ME/XP: C:\Windows\Installer
In Windows 2000: C:\WinNT\Installer
· Right-click the first file in the list with a “.msi” extension.
Click Properties > Summary.
If either the Subject or Author fields contains a reference to Norton or Symantec, click OK and then press Delete to remove that file.delete that file.
If there are no more files with an “.msi” extension, proceed to step 10, otherwise right-click the next file in the list with an “.msi” extension and go back to step 6.
Try to reinstall the NIS. If you receive the same error, then continue to the next section.

To reinstall the Microsoft Installer
Both NIS and Norton AntiVirus 2004 use the Microsoft Installer. To install the latest version of the Microsoft Installer see the documents Windows Installer 1.1 Redistributable for Windows 95 and 98 <http://www.microsoft.com/downloads/details.aspx?
displaylang=en&FamilyID=F1B7A5B0-611B-45A7-A06D-CADFF33E64DA>
(this document contains MSI updates for Windows 98, ME, and 2000), and Links to Microsoft information about how to reinstall the Microsoft Installer (MSI) <http://service1.symantec.com/SUPPORT/tsgeninfo.nsf/docid/2001092110452312>.

How to use the Bootrec.exe tool in the Windows Recovery Environment to troubleshoot and repair startup issues in Windows Vista

Published on February 9, 2010 in English, Tweaks, Uncategorized and Windows Vista. 0 Comments

You can use the Bootrec.exe tool in the Windows Recovery Environment (Windows RE) to troubleshoot and repair the following items in Windows Vista: • A master boot record (MBR) 
• A boot sector 
• A Boot Configuration Data (BCD) store 
Note When you are troubleshooting startup issues by using the Windows RE, you should first try the Startup Repair option in the System Recovery Options dialog box. If the Startup Repair option does not resolve the issue, or if you must troubleshoot more steps manually, use the Bootrec.exe tool.
MORE INFORMATION
To run the Bootrec.exe tool, you must start the Windows RE. To do this, follow these steps: 1.  Put the Windows Vista installation disc in the disc drive, and then start the computer. 
2.  Press a key when you are prompted. 
3.  Select a language, a time, a currency, a keyboard or an input method, and then click Next. 
4.  Click Repair your computer. 
5.  Click the operating system that you want to repair, and then click Next. 
6.  In the System Recovery Options dialog box, click Command Prompt. 
7.  Type Bootrec.exe , and then press ENTER. 

Bootrec.exe options
The Bootrec.exe tool supports the following options. Use the option that is appropriate for your situation.
/FixMbr
The /FixMbr option writes a Windows Vista-compatible MBR to the system partition. This option does not overwrite the existing partition table. Use this option when you must resolve MBR corruption issues, or when you have to remove non-standard code from the MBR.
/FixBoot
The /FixBoot option writes a new boot sector to the system partition by using a boot sector that is compatible with Windows Vista. Use this option if one of the following conditions is true: • The boot sector has been replaced with a non-standard Windows Vista boot sector. 
• The boot sector is damaged. 
• An earlier Windows operating system has been installed after Windows Vista was installed. In this scenario, the computer starts by using Windows NT Loader (NTLDR) instead of Windows Boot Manager (Bootmgr.exe). 

/ScanOs
The /ScanOs option scans all disks for installations that are compatible with Windows Vista. Additionally, this option displays the entries that are currently not in the BCD store. Use this option when there are Windows Vista installations that the Boot Manager menu does not list.
/RebuildBcd
The /RebuildBcd option scans all disks for installations that are compatible with Windows Vista. Additionally, this option lets you select the installations that you want to add to the BCD store. Use this option when you must completely rebuild the BCD.

Note If rebuilding the BCD does not resolve the startup issue, you can export and delete the BCD, and then run this option again. By doing this, you make sure that the BCD is completely rebuilt. To do this, type the following commands at the Windows RE command prompt: • bcdedit /export C:\BCD_Backup 
• ren c:\boot\bcd bcd.old 
• bootrec /RebuildBcd

How to troubleshoot application compatibility issues in Windows Vista

Published on February 7, 2010 in English, Tweaks and Windows Vista. 0 Comments

http://support.microsoft.com/kb/927386/en-us

How to troubleshoot scenarios in which the rollback phase was unsuccessful after you upgrade from Windows XP to Windows Vista

Published on February 7, 2010 in English, Windows Vista and Windows XP. 0 Comments

INTRODUCTION
If you upgrade a computer from Microsoft Windows XP to Windows Vista, and if an error occurs during setup, the rollback phase is initiated. The rollback phase returns the computer to the previous operating system installation.

This article describes a successful and unsuccessful rollback phase. The article also describes how to troubleshoot scenarios in which the rollback phase was unsuccessful.
MORE INFORMATION
When an error occurs during a Windows Vista upgrade installation, the rollback phase may be successful or unsuccessful.
Successful rollback phase
When the rollback phase is successful, you can start Windows XP on the computer. The rollback process restores your personal data files to their original locations on the hard disk.

After a successful rollback phase, follow these steps: 1.  Make sure that your personal data files are in the correct location. If your personal data files are missing, they may be located in one or more of the following folders: • \$WINDOWS.~Q\DATA\Documents and Settings\ Username 
• \$INPLACE.~TR\Machine\Data\DATA\Documents and Settings\ Username 
• \Users\ Username 
 
2.  Examine the setup log files to determine the cause of the installation failure. The log files from a failed upgrade are located in the \$Windows.~BT\Sources\Panther folder on the hard disk partition that contains the startup files.

MICROSOFT INTERNAL SUPPORT INFORMATION
For more information about Windows Vista setup log file locations, click the following article number to view the article in the Microsoft Knowledge Base:
927521 Windows Vista setup log file locations
Unsuccessful rollback phase
When the rollback phase is unsuccessful, you may experience any of the following symptoms: • The operating system does not start, or you receive an error message when you try to start the operating system. 
• You receive a “Rollback Setup” message every time that you start the operating system. 
• When you try to start the previous operating system installation, you receive an error message that resembles the following error message:
Windows could not start because the following file is missing or corrupt: File name 
These symptoms may occur for any of the following reasons: • The boot sector on the hard disk is still using the Windows Boot Manager (Bootmgr.exe) instead of Windows NT Loader (NTLDR). 
• The rollback data for the installation is corrupted or is inaccessible. 
• The rollback phase was not completed successfully. 

How to troubleshoot an unsuccessful rollback phase
To troubleshoot an unsuccessful rollback phase, you should first try to preserve your personal data files on the hard disk. Then, prepare the computer so that you can reinstall the operating system. To do this, use one of the following methods, as appropriate for your situation.
Method 1: Restore the boot sector
When you start the computer, you may see the Windows Boot Manager menu. This menu includes options to start Windows Vista and Windows Setup. If this menu appears, select the Previous Operating System option.

If the previous operating system starts successfully, the rollback phase was partially completed. To complete the rollback to the previous operating system installation, follow these steps: 1.  Start the Windows Recovery Environment, and then open a command prompt. To do this, follow these steps: a.  Put the Windows Vista installation disc in the disc drive, and then restart the computer. 
b.  Press a key when you are prompted to restart from the disc. 
c.  Select a language, a time, a currency, and a keyboard or an input method, and then click Next. 
d.  Click Repair your computer. 
e.  Click the operating system that you want to repair, and then click Next. 
f.  In the System Recovery Options dialog box, click Command Prompt. 
 
2.  Restore the boot sector so that it uses NTLDR instead of the Windows Boot Manager. To do this, type the following command, and then press ENTER:
bootsect /nt52 SYS 
3.  Make sure that your personal data files are in the correct location. If your personal data files are missing, they may be located in one or more of the following folders: • \$WINDOWS.~Q\DATA\Documents and Settings\ Username 
• \$INPLACE.~TR\Machine\Data\DATA\Documents and Settings\ Username 
• \Users\ Username 
• \Document and Settings\ Username 
 
If you cannot start the previous operating system, use one of the following methods to access your personal data files. By using one of these methods, you can obtain a working environment on the computer. In this environment, you can back up your personal data files and do additional troubleshooting.
Method 2: Install Windows Vista in a new folder
You can install Windows Vista in a new folder. This configuration is known as a parallel installation. After the Windows Vista installation is complete, you can access your personal data files by using Microsoft Windows.

If you install Windows Vista in a new folder, remember the following important points: • You must click Custom Install when you select the installation type during setup. 
• Make sure that you leave the partition intact. Do not use any advanced operations on the hard disk drive. 
• After a successful installation, your personal data files are located in the following folder:
\Windows.OLD\Documents and Settings
You can also use the search feature in Windows Vista to locate your personal data files. After you locate the files, you can manually move them to the location that you want by using Windows Explorer. 
• Because this is a custom installation, programs that were previously installed on Windows XP must be reinstalled in Windows Vista. Such programs include Microsoft Office. 

Method 3: Install Windows XP in a new folder
If you cannot install Windows Vista because of unresolved compatibility issues, you can install Windows XP in a new folder. This configuration is known as a parallel installation.

If you install Windows XP in a new folder, remember the following important points: • Parallel installations should be installed on separate hard disk partitions. If you cannot do this, you can install Windows XP on the same partition as the current installation by specifying a new folder name during setup. However, there is a possibility of data loss. The “Program Files” folder and the “Documents and Settings” folder may be overwritten.

Therefore, it is best not to use the parallel installation over a long time. You should use this method only temporarily to access and to back up your personal data files. 
• After a successful parallel installation, your personal data files may be located in one or more of the following folders: • \$WINDOWS.~Q\DATA\Documents and Settings\ Username 
• \$INPLACE.~TR\Machine\Data\DATA\Documents and Settings\ Username 
• \Users\ Username 
You can also use the search feature in Windows to locate your personal data files. After you locate the files, you can manually move them to the location that you want by using the drag-and-drop feature in Windows. 
• After the parallel installation is complete, you must reinstall your programs, the latest service pack, and the latest critical updates. 

How to perform a parallel installation of Windows XP
Method 4: Use the command prompt in the Windows Recovery Environment
This method is the quickest way to access your personal data files. However, the command prompt is more complex to use than the drag-and-drop feature in Windows.

If you are confident that you can use the command prompt to manually copy files, this method is the most direct way to complete a backup. After the backup is complete, you can format the hard disk and perform a clean installation of the operating system.

To start the Windows Recovery Environment and to open a command prompt, follow these steps: 1.  Put the Windows Vista installation disc in the disc drive, and then restart the computer. 
2.  Press a key when you are prompted to restart from the disc. 
3.  Select a language, a time, a currency, and a keyboard or an input method, and then click Next. 
4.  Click Repair your computer. 
5.  Click the operating system that you want to repair, and then click Next. 
6.  In the System Recovery Options dialog box, click Command Prompt.

Error message when you try to start Windows Movie Maker in Windows Vista: “Movie Maker has stopped working”

Published on February 7, 2010 in English and Windows Moviemaker. 0 Comments

SYMPTOMS
When you try to start Microsoft Windows Movie Maker on a Windows Vista-based computer, you may receive an error message that resembles the following:
Windows Movie Maker has stopped working
Windows Movie Maker does not start.
CAUSE
This issue can occur if an incompatible video filter is installed on the computer.
RESOLUTION
To resolve this problem, start Movie Maker in safe mode, and then configure Movie Maker so that the incompatible video filter is not loaded.

To do this, follow these steps: 1.  Click Start, and then click All Programs. 
2.  Click Accessories, and then click Command Prompt. 
3.  At the command prompt, type CD \program files\movie maker , and then press ENTER. 
4.  Type moviemk.exe /safemode , and then press ENTER. 
5.  When Movie Maker starts, click Tools, and then click Options. 
6.  Click the Compatibility tab. 
7.  In the Filters section, click to clear the check boxes of any third-party video filters that are not required. 

MORE INFORMATION
A video filter is a component that is used to decode audio and video. Movie Maker supports several different video formats. Movie Maker tries to use the appropriate filter when a filter is needed. In some cases, Movie Maker tries to use an incompatible filter. This can cause Movie Maker to stop working. You can use the Compatibility tab to disable third-party components and codecs so that they are not used. However, sometimes Movie Maker stops working before you can configure these settings. In these scenarios, you can use the Safemode command switch option to make the needed changes.

5 visitors online now
5 guests, 0 members
Max visitors today: 5 at 09:35 am CEST
This month: 13 at 09-02-2010 05:29 am CEST
This year: 37 at 04-02-2010 08:56 pm CEST
All time: 37 at 04-02-2010 08:56 pm CEST