2020. 1. 25. 05:54ㆍ카테고리 없음
'Could not complete scan' error when using Windows Fax and Scan with a HP OfficeJet Pro 8600 Plus All-In-One network printer. Printing is fine. When using the HP Scan application, get the error 'Scanner communication cannot be established'. When scanning from the printer itself it fails with the same message. In addition the printer panel displays the error: 'The scan could not be completed due to one or more of the following issues: Connection to the computer is lost The scanner is in use OCR application is not installed' My PC is a HP Compaq Pro 6300 SFF 64bit, with ethernet cable to the router and ethernet cable to the printer Originally ran Windows 8.0; recently upgraded to Windows 8.1. Older separate Netgear router and modem was replaced with a newer Netgear Router/Modem, but both experienced the same problem.
A Symantec Endpoint Protection (SEP) 14 scan does not appear to complete and seems to be running for several days or longer. The scan is configured with.
There was no problem with the original Windows 8.0 configuration and only after upgrading to 8.1 did the problem emerge. On my home netowrk I have an HP ProBook 6550b running Windows 7 sp1 that uses wireless to get to the Router, and it has no problem with scanning.
I have followed the recommendations of a number of articles relating to this issue (including: but there has been no change in behaviour. The printer has a static IP address; Power settings have been adjusted to Never for Turn off Hard Disk; Sleep and Hybrid Sleep. Scanning has been tested with all firewalls and antivirus turned off and in Selective Startup. The printer has been plugged directly into the power socket. With all these settings the Windows 8.1 cannot scan while the Windows 7 laptop with wireless to the router has no problems. Appreciate any insights into this problem.
I can only surmise that the problem is a compatibility problem between the 8600 Printer and Windows 8.1. Regards, Motorbike.
If Full Scan runs excessively long or have a significant difference from your previous scans, hangs or crash the system, Follow the steps below on running a Windows Maintenance Check first. If issue still persist, select the appropriate topic below for further troubleshooting: Windows Maintenance Check Files tend to accumulate as time goes on when a computer is used. It is essential to run regular system maintenance to assure the optimal performance of your system and to eliminate the scanning of unnecessary files. Perform regular system maintenance and clean up.
This includes checking the hard disk for errors via Check Disk, System File Check, Disk Defragment, Disk Cleanup, and generally maintaining the computer from running programs that are taking up resources unnecessarily. Click the appropriate link for steps on how to run Windows Maintenance Check. If the above does not correct the issue, disable the Scan inside archives option and the Scan for Rootkit option from the Settings. In order to bring about a resolution to this problem, we must find out what file the scanner is hanging on. Once the log information or file has been collected contact so the files can be analyzed.
There are 2 ways to come about this information. Option 1 Run a portable scanner VIPRE Rescue. The executable runs the same engine as VIPRE and should also hang on the same object being scanned.
Click this link for steps on. During the scan process, log information is created in C: VIPRERescue. Collect the log files in this folder, generally named YYYYDDMMhhmmss.csv with the current date and time. The last file indicated by VIPRE Rescue is a generic area where the VIPRE scan is hanging. Option 2 Run the VIPRE deep scan with the Scan Progress window open. Once the scan progress stops on a certain file, this usually indicates where the scan is actually hanging.
Take note of the whole file address and contact to have the file analyzed. A more accurate account account on where VIPRE scan is hanging can be found in the SBAMThreatEngineLog.csv file that is created in the Log file location for VIPRE. The files can be located at:.
Windows XP:%ALLUSERSPROFILE% Application Data VIPRE Logs. Windows Vista 7 8:%ProgramDATA% VIPRE Logs It can be difficult analyzing this log to figure out the last file VIPRE scanned so it is recommended that assistance from support specialist is requested once the file has been gathered. Rapid Scan is a feature used to drastically reduce scan times, it avoids re-scanning files that are known to be safe based on previous scans, thus cutting the scan times by 20%. To use this feature, you need to add a new schedule scan or use an already existing scheduled scan. Click the drop down arrow key from the Schedule scan. Click the pencil icon to edit an existing scheduled scan or +new scan to create a new one. Set your schedule scan and put a check mark under the Scan Option box to enable VIPRE Rapid Scan.
Run you scan again and see if it significantly reduced the scan time. If you are running VIPRE scan and its been on the same file for a period of time, that means that VIPRE scan is stuck on that file and cannot continue to scan the next file. To resolve this issue, the said file needs to be whitelisted.
Follow the steps below:. Take note of the address of the file where the scan is stuck. Open VIPRE. Select the Manage tab and click Antivirus.
Scroll down till you see Exclude from Scans. Click Manage Excluded Items. Click the Add New Location or File to add exclusions and run the VIPRE scan again.
When you get a message Scan fail or your Scan History has no history created for scans previously ran, it is likely because the History folder in the volatile data directory for VIPRE does not have any XML files created in it. This can sometimes indicate a problem with the permission associated to the History folder or that MSXML.dll files need to be re-registered. Re-registering MSXML.dll files:.
Navigate to the system32 folder (C: Windows System32). Browse doe files that are names MSXML#.dll, where a number from 2-6 will be in-place of '#' depending on the version of MSXML that is installed on the system. Click Start Run (Windows XP) or Start and type in the search option Run and press enter. Enter regsvr32.exe MSXML#.dll for each MSXML#.dll you find in the System32 folder If the regsvr32.exe MSXML#.dll fails, note the error message and consult Microsoft.
Errors in this process are permissions related and can be fixed relatively easily via Microsoft provided tools or hot fixes. Once all MSXML files have been registered successfully, attempt to run a scan again and it should complete and create history information. If it does not, there is likely a problem with the history folder itself or the MSXML.dll needs to be re-registered. Navigate to the system32 folder C: Windows System32.
Browse for files that are names MSXML#.dll, where a number from 2-6 will be in place of # depending on the version of MSXML that is installed on the system. Click Windows key + R to open the Run box. Enter regsvr32.exe MSXML#.dll for each MSXML#.dll you find in the System32 folder If the regsvr32.exe MSXML#.dll command fails, note the error message and consult Microsoft. Generally speaking, errors in this process are permissions related and can be fixed relatively easy via some Microsoft provided tools or hotfixes. Once all MSXML files have been registered successfully, attempt to run and a scan again and it should complete and create history information. If it does not, there is likely a problem with the history folder itself.
In some scenarios, this issue is caused by broken permission for the ProgramData or Application Data folders. The easiest way to fix a problem with these folders is to reset permissions on the directory in question. This can be done manually by comparing the permissions on the folder to another installation of Windows with the correct permission set on the folder in question.
An easier way of doing this would be to just reset the permissions to that of the parent folder. A quick and easy tool can be used to achieve this: Download this application and place it on your desktop. You can then drag and drop the file or folder you intend to reset permissions on over the top of this application in order to reset the permissions for it.
Kaspersky Full Scan Will Not Complete
If done correctly, a prompt displaying the text OK will pop-up. This indicates successful execution of the application. Folders that are particularly susceptible to permission corruption are listed below. Windows XP.%ALLUSERSPROFILE% Application Data.%ALLUSERSPROFILE% Application VIPRE.%ALLUSERSPROFILE% Application Data.%ALLUSERSPROFILE% Application Data VIPRE Windows Vista 7 8 10.
C: ProgramData.%ProgramData% VIPRE.%AppData% ApplicationData VIPRE. It is a good idea to run a scan on the types of files stored on your system that might be causing part of the problem. There are certain file types that will take a long time to process no matter what is done to improve scan performance. Some good example of these file types:.
zip, rar, etc.: These file types are considered Archive Files. Whenever VIPRE has to scan an archive must first be decompressed. This process can cause scans to increase dramatically depending on the number of files and the size of them.
eml, msg, etc.: Email messages saved locally onto the computer can often mount up to many many thousands. This can easily cause scan times to increase dramatically depending on the kinds of emails being saves.
mpg, avi, mpeg, etc.: Video media files can take a long time to scan due to the sheer size of the files. Here is a neat tool that can be used to identify what kinds of files are taking up the most space on your system: There are a lot if information ont he site on how to user this. Basically, you want to install the program and run a scan with it. It will list the file types taking up the most space on the system on the right hand side once the scan is complete. You'll want to consider the top 5 file types that are listed, ignoring file types like dll, sys and exe.
Avast Will Not Complete Scan
Exceptions can then be made in VIPRE regarding the file types taking up the most space in order to test scan speeds with the files excluded. If scan times improve dramatically, you can consider moving the files to less often scanned location or dealing with them by other means. Did you find it helpful?