Some diagnostic packages on Windows 8 may require installation of. NET Framework 3. Usually there are no restart requirements for installing the minimum prerequisites. However, there will be some situations in which a restart will be necessary. For example, your computer has PowerShell 1. If the destination computer is running Windows XP, Windows Server , Windows Vista, or Windows Server and you cannot install PowerShell, you may be able to run a reduced functionality version of the diagnostic package.
However, there may not be an equivalent "Reduced Functionality" package available for every diagnostic. In addition, reduced functionality packages may not collect the full set of data that is collected by a standard package it may only be able to collect a subset.
In order to determine whether you can run a reduced functionality package that does not require installation of the minimum prerequisites listed in Q6, open the URL that was provided by Microsoft in the email message and expand the "Additional methods to run this diagnostic package" section.
If you see the text labeled "On Windows XP, Windows Server , Windows Vista, or Windows Server ," this means that a reduced functionality version of the package can be run on the computer.
In this case, you can expand the section and then click the "Run diagnostic" link. The following article contains more information about how to run reduced functionality packages:.
As described in Q3, some settings, or run-time components may remain on the computer. For example, if PowerShell was installed during the execution of a diagnostic package, PowerShell will remain on the computer. These folders are deleted after the diagnostic package has finished running. Most of the diagnostic packages do not make any changes to the PowerShell execution policy. However, some diagnostic packages that collect information from remote computers may alter the PowerShell execution policy to "RemoteSigned" temporarily.
The diagnostic package will change the configuration back to the original policy before it finishes collecting the information. Be aware that the policy may remain "RemoteSigned" if you cancel the diagnostic before the package finishes running. Windows Server R2 Server Core does not support running diagnostic packages directly on the computer. In order to diagnose a Windows Server R2 Server Core computer, you will have to contact your support engineer and request a passkey to run a specific diagnostic package that can be used to collect information from a Server Core R2 computer by using a remote computer.
This message is generated by the "System Information" utility MSInfo32 when it is collecting information about the computer. A diagnostic package usually runs the msinfo32 utility in the background, while executing other diagnostic tasks in the foreground, to speed up the data collection process.
This process only collects information about the system and does not update any settings on the computer. If you are not sure as to which computers to run the diagnostic packages on, please discuss the issue further with a Microsoft support engineer. The data that is uploaded by a diagnostic package is used for troubleshooting. We will not disclose any information that is included in the results outside of Microsoft, its controlled subsidiaries, and its affiliates without your consent.
Microsoft is committed to protecting the security of your personal information. We use many different security technologies and procedures to help protect your personal information from unauthorized access, use, or disclosure. For example, we store the personal information that we collect on computer systems with limited access, which are located in controlled facilities.
When we transmit highly confidential information over the Internet, we protect it by using encryption, such as the Secure Socket Layer SSL protocol. This section discusses the most common problems that may occur when you run diagnostic packages on a computer.
This may occur because the diagnostic package that you are trying to run is incompatible with the operating system of the destination computer. For example, you may be running Windows XP but the diagnostic package that Microsoft Support has sent you is only compatible with Windows 7. In this case, please contact a Microsoft Support professional to ask for a diagnostic that is compatible with the operating system of the destination computer.
Then click Run in the File Download dialog box, and follow the steps in the Fix it wizard. This usually happens when the computer cannot contact Microsoft servers to download client components or the diagnostic package. Sorry this didn't help. Thanks for your feedback. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question 9. Report abuse.
Details required :. Select registration option. Error: Javascript is disabled in this browser. This page requires Javascript. Modify your browser's settings to allow Javascript to execute. See your browser's documentation for specific instructions. HP Customer Support. Select your model. How does HP install software and gather data? Apache Log4j Update Please see this document here for current information regarding the Apache Log4j vulnerability.
Need Windows 11 help? This document is for HP and Compaq computers with Windows 10 or 8. This document describes how to use the automated troubleshooting tools in Windows. These tools use a combination of installed and online applications to detect and resolve many computer problems, such as problems with networking, system performance, and hardware devices.
For business computers , automated troubleshooting tools might not available. Contact your company's IT department or your local IT service to resolve issues. Automated Troubleshooting tools Use automated troubleshooting tools to detect and resolve many computer problems. Run the troubleshooting tool that matches the problem on your computer. Upon completion, a report generates that lists any messages and resolved problems it found.
The Troubleshoot computer problems window contains four categories of troubleshooting tools. In Windows, search for and open Control Panel. In the Control Panel search field, type troubleshooting , and then click Troubleshooting in the search results. The Troubleshoot computer problems window opens. Review the following categories before you make a decision. Programs Use these tools to identify problems related to software applications, drivers, and utilities that are installed on your computer.
Network : Checks network and internet connections. Web Browser : Checks that the web browser is functioning correctly, that the security settings are adequate, and that the web browser performance is maximized if available.
Printing : Confirms that printer drivers are installed, and that printers are functioning correctly. Sound : Checks audio hardware, plays sounds and music files, records sound from microphone or other recording device. Network : Checks networking hardware, such as Ethernet, wireless, or other network adapters.
0コメント