How to Fix fltmgr.sys in Windows 10

The fltmgr.sys file or the Filter Manager is the one that’s responsible in making sure that all the file stored in a computer’s hard drive stays on their respective locations and is located in C:/Windows/System32/drivers. Now when you encounter a Blue Screen of Death or BSOD error saying, “Your PC ran into a problem that it couldn’t handle, and now it needs to restart. SYSTEM_SERVICE_EXCEPTION”. This kind of Stop error is due to an error with the driver that’s responsible for enabling the communication between the hardware and the computer. It indicates that this driver allows direct access to the internal hardware from the CPU itself.

What’s worse about the SYSTEM_SERVICE_EXCEPTION BSOD error is that there are times when you won’t be able to log in to your computer even after it reboots. However, you need not worry as this post will guide you into fixing this BSOD error. All you have to do is follow the given options below carefully and that before you proceed make sure that you create a System Restore point just in case something goes wrong.

Option 1 – Run the Windows Update

Obviously, since the fltmgr.sys file is a system file from Microsoft, you can try running the Windows Update and see if it fixes the problem or not.

Option 2 – Run the System File Checker

The System File Checker, also known as the SFC scan, is a built-in utility in Windows that can be found in the C:/Windows/System32 folder. This tool allows you to scan and restore any corrupted system files in Windows that might be causing the SYSTEM_SERVICE_EXCEPTION BSOD error. To use this tool, follow the steps below.

  • Tap Win + R to launch Run.
  • Type in cmd in the field and tap Enter.
  • After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

  1. Windows Resource Protection did not find any integrity violations.
  2. Windows Resource Protection found corrupt files and successfully repaired them.
  3. Windows Resource Protection found corrupt files but was unable to fix some of them.
  • Restart your computer and then check if it has fixed the error or not.

Option 3 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that can be found on the Settings Troubleshooters page. To use it, refer to these steps:

  • Tap the Win + I keys to open the Settings panel.
  • Then go to Update & Security > Troubleshoot.
  • From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Option 4 – Check your hardware for any physical issues

There are times when faulty hardware can result in serious problems in the system such as the SYSTEM_SERVICE_EXCEPTION Blue Screen error. Thus, it is highly recommended that you check the internal components of your CPU to find out if there are any problems. And if there is any physical damage, you need to bring that to a technician to get it fixed or have it replaced.

Option 5 – Run the CHKDSK utility

You can also run the Chkdsk utility to resolve the BSOD error. The Chkdsk utility is the one that repairs hard drive errors that might be causing the problem.

  • Open Command Prompt with admin privileges.
  • After opening Command Prompt, execute the commands listed below, and don’t forget to hit Enter right after you type in each one of them and if you have installed Windows to some different directory, you must replace “C” with the name of the drive you’ve installed Windows with.
  • chkdsk C: /r /x
  • chkdsk C: /f

Do You Need Help with Your Device?

Our Team of Experts May Help
Troubleshoot.Tech Experts are There for You!
Replace damaged files
Restore performance
Free disk space
Remove Malware
Protects WEB browser
Remove Viruses
Stop PC freezing
GET HELP
Troubleshoot.Tech experts work with all versions of Microsoft Windows including Windows 11, with Android, Mac, and more.

Share this article:

You might also like

How to Fix Remote Desktop Black Screen issues
According to some reports, using RDP or Remote Desktop Protocol on recent versions of Windows 10 results in a black screen. One encounters this issue is when using the Remote Desktop Connection feature on Windows 10. The real causes of this black screen are either the display drivers or some misconfiguration with the Remote Desktop Connection utility. In most cases, the Remote Desktop in Windows 10 will display a black screen and then disconnects afterward. To fix this kind of issue on your Remote Desktop, there are two suggestions you need to check out. First, you can try to disable the persistent bitmap caching, and then you can also try to update your display driver. Follow the given options below for more troubleshooting instructions.

Option 1 – Try to disable Persistent Bitmap caching

The first thing you can do to resolve the black screen issue with the remote desktop is to disable the persistent bitmap caching. All you have to do is follow these steps:
  • First, open the Remote Desktop Connection client.
  • Next, click on the Show Options button to configure the Remote Desktop Connection.
  • After that, go to the Experience tab and uncheck the Persistent bitmap caching option.
  • Once done, you should now be able to connect to the remote computer without the black screen.

Option 2 – Try to update or rollback the Graphics driver

You can try to update your Graphics card driver using the Device Manager in your computer to resolve the blank dialog boxes problem or you can also go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it. To update your Graphics driver via Device Manager, refer to these steps:
  • First, boot your computer into Safe Mode.
  • After that, tap the Win + R keys to launch Run.
  • Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
  • After that, a list of device drivers will be displayed. From there, look for the Display Adapters and click on them.
  • After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
  • Now restart your computer.
  • After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.
Note: If updating the Graphics driver didn’t fix the problem, you can also try to roll back to its previous version and see if that helps or you could also try to roll back, update or reinstall the Network Adapter drivers.

Option 3 – Try performing a System Restore

You might also want to perform a System Restore that might help you in fixing the error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.
  • Tap the Win + R keys to open the Run dialog box.
  • After that, type in “sysdm.cpl” in the field and tap Enter.
  • Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
  • After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.
Read More
Command prompt tips and tricks
Hello and welcome to errortools articles. Today we will talk about some great and awesome tips and tricks for the command prompt. Commands which can make your life easier and your workday more pleasant. That being said let's dive in right into muddy waters and swim out with new knowledge.

Tip 1: Read Motherboard information

There are a lot of reasons why you would like to read information from your motherboard, maybe you would like to upgrade your BIOS, perhaps you would like to know the serial number, maybe even the version number. Well, you can, type the following code into the command prompt and you will receive all information about your motherboard.
wmic baseboard get product,version,serialnumber,product

Tip 2: Copy command output to clipboard

Getting information from the command prompt to a word processor, into an email or any other medium can be somewhat troublesome, usually, people tend to screenshot or write from a command prompt into another destination, which could induce errors, and let's be honest, it is not practical. You can copy command output directly into the clipboard ready for pasting it anywhere with | clip. So for example if you would like to paste the directory structure of your c drive command would look like: dir c: | clip, now output would be placed into the clipboard ready to be pasted anywhere needed.

Tip 3: Erase data permanently

When you delete data on your hard drive, what really happens is that files are marked with a marker which marks that space for new data writing, but the data itself is still present and can be brought back. This sometimes could impose problems but if you would type: cipher /w:c Windows will write random data over each marked file deleting it forever without means to be brought back.

Tip 4: Manage your IP address

If you would like to play with your IP address and do fancy stuff with it do the following: ipconfig /release to release your IP address ipconfig /renew to renew your IP address ipconfig /flushdns to flush down DNS information and enjoy a new browsing start.

Tip 5: Check to see are packets reaching the desired location

You installed a new LAN printer, or a new switch, maybe you want to check if your new site is up and running. Use ping destination in order to see if TCP packets are reaching desired information, you can use it with a specific address like ping 192.168.1.1 or you can type a web address, for example, ping google.com and see if a connection can be established.

Tip 6: Get information about a specific command

So you learned some command prompt commands, but you do not know all of their configuration or switches? No worries, just type command/? to get a list of available switches for it. For example ipconfig/? will write you a list of available switches for ipconfig command.

Tip 7: Link and execute multiple commands one after another.

Let us say that for example, you would like to copy files into a different folder, then rename some and delete others and you need to do a couple of times. Instead of writing command after command once each one is finished link them with && and they will execute one after another.

Tip 8: Scan and repair files.

In order to scan files and repair broke or corrupted ones write in the command prompt: sfc /scannow. Please know that this command can take a long time since it is solely dependant on the number of files, their size, and the power of the computer.

Tip 9: Manage and configure your computer energy

Command powercfg will let you manage and see the power configuration of your computer. Just write powercfg/? and see what you need and want to change or get information about.

Tip 10: Associate files with applications

Windows already has some file associations defined, and some applications take over some type of files but if you want to take control into your own hand use assoc command. For example assoc.txt= "APPLICATION NAME" will associate txt files with the provided application.

Tip 11: Hide files and folder.

Do you have some folder or file with information that you do not want to be seen when someone opens file explorer? Use attrib +h <name of file> and hide file or attrib +h /D <folder name> to hide folder.

Tip 12: Get a list of installed computer drivers

Want to know which drivers are installed in your system? Use driverquery and take a look.

Tip 13: Find and locate shared folders

have you shared a folder but forgot which one and where? Do not bang your head on the wall, we have a simple solution for you. just type in command prompt net share and see everything.

Tip 14: Run commands as an administrator

You do not have administrator privileges? Do you want to bypass common blockades?
runas /user:yourdomainadministrator command
That is all that we have for you today, I certainly hope you have found something useful here and that we have managed to teach you some valuable things.
Read More
Selected boot image did not authenticate Error
If you are using UEFI and you encountered an error message that says, “Selected boot image did not authenticate”, then read on as this post will show you what to do it fix it. This kind of error indicates that UEFI is having an issue in figuring out if the boot image has tampered with. UEFI offers Secure Boot and if the boot image seems to be invalid, you won’t be allowed to boot into your computer. Aside from that, it could be that you may be using endpoint encryption and the software can’t validate the certificate. To fix the “Selected boot image did not authenticate” error in UEFI, you need to first check if the error has given any reference to any software that you might have for encryption. If it has, then you need to disable the Encryption tool to resolve the problem. In addition, you could also try to disable Secure Boot or perform Startup Repair in case the disabling Encryption tool didn’t work. For more details, make sure to use each one of the options provided below as a reference.

Option 1 – Try to disable the Encryption tool

The first thing you can do to fix the “Selected boot image did not authenticate” error is to disable the Encryption tool. Many users reported that some encryption tools like the ESET Endpoint Encryption won’t let them boot into the computer if the system manufacturer does not include the correct certifications as a part of the UEFI BIOS. And since there is no way to bypass this, you have to disable Secure Boot in order for you to boot into your computer.

Option 2 – Disable the Secure Boot in the BIOS

Disabling the Secure Boot in the BIOS settings is definitely recommended to resolve the error. To disable Secure Boot, here’s what you have to do:
  • First, boot your computer into Windows 10.
  • Next, go to Settings > Windows Update. From there, check if there is anything that you have to download and install if you see any available updates. Usually, OEMs send and update the list of trusted hardware, drivers, and operating systems for your computer.
  • After that, go to the BIOS of your computer.
  • Then go to Settings > Update & Security > Advanced Startup options. If you click on Restart Now, it will restart your computer and give you all the advanced options.
  • Next, select Troubleshoot > Advanced Options. As you can see, this screen offers you further options including System restore, Startup repair, Go back to the previous version, Command Prompt, System Image Recovery, and UEFI Firmware Settings.
  • Select the UEFI Firmware Settings which will take you to the BIOS.
  • From there, go to the Security > Boot > Authentication tab where you should see Secure Boot. Note that every OEM has its own way of implementing the options so it varies.
  • Next, set Secure Boot to Disabled and set Legacy Support to On or Enabled.
  • Save the changes made and exit. Afterward, your computer will reboot.

Option 3 – Try to run the Automatic Repair Utility

If disabling Secure Boot did not fix the problem, you might also want to run the Automatic Repair utility in fixing the error. To do so, follow the steps below.
  • You can start by booting into the Advanced Recovery Mode.
  • After that, select Troubleshoot > Startup Repair.
  • Next, follow the on-screen instructions that appear on the screen and finish the Automatic Repair process.
  • Now check if the block is gone once the reboot is completed.
Read More
How to Fix Logon.scr Application Error

Logon.scr Application Error - What is it?

To understand Logon.scr application error, it is first important to understand the function of logon.scr. Logon.scr is an important file that is located in the Windows\System32 folder. It guarantees Windows systems stability. Logon.scr application error occurs when logon.scr file gets corrupt. It is a common system error that can happen in most Windows platforms. It usually pops up during system start-ups and when trying to launch certain programs. Some of the common systems of this error code include: system halt, freeze, no application icons are visible on the desktop, random blue screen of death and system performance decreases dramatically.

Solution

Restoro box imageError Causes

Two of the most common causes of logon.scr application error is:
  • Corrupted and damaged logon.scr file
  • Viral infection
It is advisable to fix this error code immediately because it leads to serious damages. It is fatal and can result in a system crash; therefore resolve it right away.

Further Information and Manual Repair

To resolve this issue on your computer you don’t have to spend hundreds of dollars to hire a professional for the job. The good news is that it can be repaired easily and does not require any technical expertise. Here are some of the most effective and easy DIY methods to resolve the error on your screens.

Method 1 - Replace the Damaged and the Corrupted Logon.scr File

Whether the file gets corrupted or is accidentally deleted, the best way to fix the issue is to download the Logon.scr file again from a reliable website and install in the following location C:\Windows\System32. Alternatively you can also get the file copy form another proper functioning computer by using flash drive if you don’t have an internet connection to download the logon.scr file online.

Method 2 - Restore Points by Applying System Restore of Windows

Another way to resolve this is to restore points to bring back your system to the previous state before the error occurred. To do this, simply click the start button and type ‘System Restore’. Now click System Restore in the result and click next. Select the restore point in the list and click the next button to proceed. To activate changes reboot your PC.

Method 3 - Scan and Remove Viruses

If Logon.scr application error still persists, then it could be due to viruses. To resolve, install a powerful anti-virus. Scan your entire PC and remove viruses.

Method 4 - Repair the Registry

Corrupt and damaged Logon.scr file also triggers issues with the registry. DLL files and other important files like Logon.scr application files may get damage due to too many bad and invalid registry entries. Registry stores all the activities performed on the PC including unnecessary files like junk files and cookies. If these are not removed timely, these files accumulate and corrupt important files. Therefore, to fix the error it is advisable to clean and repair the registry. The best way to go about is to download Restoro. This is a user-friendly and multi-functional PC Fixer deployed with a registry cleaner. It scans for all registry errors and removes all the invalid entries. It cleans the registry and repairs the damaged files thereby resolving the issue in seconds. Click here to download Restoro and resolve the Logon.scr application error now!
Read More
Enable Windows Sandbox on Windows
One of the most common ways cybercriminals use to inject suspicious code into devices is by tricking users into installing a malicious program on a targeted device. Oblivious users are vulnerable to such tricks, which is why Microsoft has been working hard in the background to address this issue. Recently, Microsoft announced the availability of a sandboxed version of Windows 10 that runs inside Windows 10 in order to isolate suspected software to run inside it and protect the system from potential threats. This Windows Sandbox feature is a new feature that keeps your computer secure. It is a virtual disposable environment that you can enable. So if suspect any software of being malicious, you can run this software in an environment and ensure that it won’t interfere with any normal processes and would not jeopardize files on your computer. To simply put it, “Windows Sandbox is a new lightweight desktop environment tailored for safely running applications in isolation”. So if the Sandbox is closed, all the residual files, software, and other data are deleted permanently. To enable Windows Sandbox, refer to the instructions provided below. Step 1: You have to make sure that you are running either Windows 10 Enterprise Editions or Windows 10 Pro and that your computer is running build 18305 or newer. Step 2: After that, you have to enable Virtualization to let another instance of Windows 10 running in Sandbox mode. Step 3: Next, search for Windows Features on and off in the search box and then select the appropriate entry. Step 4: From the list, go to the mini window and check the Windows Sandbox and then click on OK. Step 5: Afterwards, in the Cortana Search box, search for “Windows Sandbox” and select the related entry to run it in an elevated window. Step 6: Then from your main computer (host), copy the executable file and paste it inside the Windows Sandbox environment. Step 7: Now run the executable file in the Sandbox environment and use it as you normally do. Step 8: Once you’re done, close the Windows Sandbox application and as mentioned, every data regarding the executable file and the temporary environment will be deleted. Step 9: And for the sake of safety, ensure that there are no modifications made to the host because of the executions in the Sandbox environment. You have the option to contact Microsoft for feedback related to Windows Sandbox. You can use the traditional Feedback Hub if you have any suggestions or any issues. Just fill in the appropriate details and select Windows Sandbox for the feature category under the Security and Privacy section. And if you have any issues related to the execution of and within Windows Sandbox, simply choose “Recreate my problem” then select Start capture to reproduce the issue, and once you’re done, select Stop capture.
Read More
Fix HAL INITIALIZATION FAILED Error 0x0000005C
When your computer boots up or when it just woke up from sleep but it suddenly encounters a Blue Screen of Death error, saying, “HAL INITIALIZATION FAILED error with STOP CODE 0x0000005C”, then read on as this post will give you some fixes that might help in resolving the problem. You will see the following error message on your computer’s screen when this error pops up:
“Your PC ran into a problem and needs to restart. We’re just collecting some error info, and then we’ll restart for you. If you’d like to know more, you can search online later for this error: HAL_INITIALIZATION_FAILED HAL INITIALIZATION FAILED 0x0000005C”
This kind of Blue Screen error indicates that there is a hardware or device driver problem in your PC. Aside from that, it also signifies that the initialization of the Hardware Abstraction Layer or HAL has failed. This happens only during the relatively short period that the Windows operating system is being initialized, specifically during phase 4 of Windows startup. What’s worse about this kind of Stop error is that it does not just go away after a computer reboot. You may have to boot your computer into Safe mode with Networking using the Advanced startup options which you can access by tapping the F2 or F8 key. Once you’ve accessed the Advanced startup options, follow the fixes prepared below.

Option 1 – Run CHKDSK command to repair hard disk errors

Running the Chkdsk utility could help you resolve the HAL INITIALIZATION FAILED error with STOP CODE 0x0000005C. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the Chkdsk utility comes in. The Chkdsk utility repairs hard drive errors that might be causing the problem.
  • After you access the Advanced Startup options, select Command Prompt by using the arrow keys on your keyboard.
  • After opening Command Prompt, execute the following command and hit Enter:
chkdsk /f /r
  • The command you entered will scan the hard disk for any errors and will automatically fix it if it finds some issues. Wait for the process to be completed and then restart your computer.

Option 2 – Run the DISM tool

If the first option didn’t work, then running the Deployment Imaging and Servicing Management tool can help you resolve the HAL INITIALIZATION FAILED error as it will repair the Windows System Image as well as the Windows Component Store in Windows 10.
  • After you access the Advanced Startup options, select Command Prompt by using the arrow keys on your keyboard.
  • Next, type in this command: DISM /Online /Cleanup-Image /RestoreHealth
  • Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 3 – Update the Device drivers

  • Tap the Win + R keys to launch Run.
  • Type in msc into the box and tap Enter or click OK to open the Device Manager.
  • After that, a list of device drivers will be displayed. Look for the device driver you and then select either “Update driver” or “Uninstall device”. And if you find any “Unknown device”, you need to update it as well.
  • Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
  • If you have chosen to uninstall the driver, follow the screen options to complete the process and then restart your PC.
  • Connect the device and Scan for hardware changes – you can see this option under Device Manager > Action.

Option 4 – Try removing any external hardware

You might also want to remove any connected devices and external hardware in your computer as it might help in fixing the BSOD error.

Option 5 – Disable Fast Start-up

If you want your computer to boot faster, then you might have enabled Fast Start-up. This feature is ideal for computers that are using a hard disk drive. However, turning on this feature also means that when the computer boots, it might lag some drivers that are loaded when it initially boots up. Thus, it might be the potential cause of the UNEXPECTED STORE EXCEPTION BSOD error. Thus, you need to disable Fast Start-up. To do that, follow these steps:
  • Boot your PC into Safe Mode.
  • Then tap the Win + R keys to open the Run dialog box.
  • Next, type in “control” to open Control Panel.
  • After that, select Hardware and Sound and click on Power Options.
  • Select “Choose what the power buttons do” from the left side menu pane and click on Change settings that are currently unavailable.
  • Afterward, uncheck the “Turn on fast startup (Recommended)” entry and click on Save Changes.
  • Now restart your PC for the changes to take effect and then check if the problem’s fixed afterward.

Option 6 – Disable your antivirus program

There are times when the antivirus program installed in your computer blocks file access and even disk access. Thus, disabling the antivirus program or any security software installed in your computer is always a good idea you can try when the Windows Update process does not go smoothly. So before you try updating your computer again, make sure to disable the antivirus or security program and once the Windows Update is done, don’t forget to enable the antivirus program back again.

Option 7 – Perform a Clean Boot

There are some instances that some conflicting programs installed in your computer might be the one that’s causing the HAL INITIALIZATION FAILED error. To identify which program is causing the problem, you need to put your computer in a Clean Boot State. To do so, follow the steps below.
  • Log onto your PC as an administrator.
  • Type in MSConfig in the Start Search to open the System Configuration utility.
  • From there, go to the General tab and click “Selective startup”.
  • Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
  • Next, click the Services tab and select the “Hide All Microsoft Services” check box.
  • Click Disable all.
  • Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
  • From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.
Read More
Change default audio output for Narrator
For PC users that are blind or have low vision, the Narrator accessibility feature in Windows 10, lets you use your PC without a display or mouse to complete common tasks – it reads and interacts with things on the screen, like text and buttons. The narrator can be used to read and write an email, browse the internet, and work with documents. In Windows 10, there are a lot of options for Narrator that you can customize. You can change its keyboard shortcuts, personalize Narrator’s voice, enable Caps Lock warnings, and more. You can choose the voice for the Narrator, adjust the speaking rate, pitch, and volume. To change the default audio output device used to play the voice of the Narrator in Windows 10:
  • Press the ⊞ WINDOWS + I
  • From the Settings menu, click Ease of Access.
  • Click Narrator on the left pane.
  • In the Narrator window, on the right pane, toggle the button to On to enable Narrator if required.
  • Scroll down to the Personalize Narrator’s voice section.
  • For the Select where you hear Narrator’s voice option, click the drop-down and select the audio output device you want from the list. Please know that you will not be able to choose if you do not have multiple audio output devices connected to your Windows 10 computer.
  • Exit Settings when done.
If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.
Read More
Common Outlook Errors

Most Common Microsoft Outlook errors

When you have a program, you know before you even start to use it or even know how that you are going to have problems with it. There are always going to be error messages and things that don’t work on any program you buy or download; guaranteed. Even some of the most famous program developers in the world make mistakes from time to time and it is a small price to pay for the programs you get and that is a fact. Microsoft Outlook is like any other program; it has its errors. Here are some of the most common errors for Microsoft Outlook on your computer.

1. Problem receiving emails

Sometimes you can be waiting on really important emails. It is really infuriating when you know that they have been sent, however every time you check your email box, there is nothing there! Your inbox is empty and your patience is wearing thin, so could it possibly be an error with Microsoft Outlook? There is a high probability that this is the problem. The program can be a bit slow on receiving emails sometimes, often even by days. This can be caused by any number of things, from having too many emails coming through or having too many emails in your inbox. If you click ‘send and receive’ at the top, it should speed up your emails coming through, however, so give that a try if you’re waiting on anything to come through. If this doesn’t work, however, your inbox may be full. Try permanently deleting some useless messages and then click ‘send and receive’ again. All your emails should come through then!

2. General slow performance

Outlook, while it has its advantages, can often be very slow. It is probably slower than some other email programs that require a browser but it is quicker to access, which may make up for this fact. However, sometimes sluggish performance can be really irritating, so it may be wise to try and fix it if you can. One of the reasons it may be acting slow is if you have too many other Windows applications open. Applications that may interfere with your Outlook’s speed could be anything from Microsoft Word to Windows Live Messenger. If any of these are open, try closing them and see if that helps with the speed problem.

3. Corrupt files

.dbx files are not accessible by Microsoft Outlook. Therefore, they can cause problems with your emails if you have them within them. To solve this problem, you may have to delete all of your attached email accounts and then reattach them before you can open your emails again. These corrupt files can also cause you to be unable to delete emails. You will need to transfer these deleted corrupt files into a separate deletion folder as this is usually caused by the folder being corrupt. Of all the other most frequent problems with Microsoft Outlook, however, this is probably the least likely to happen, which shows how few problems there actually are with this application after all that!

Conclusion

So there are the most common problems with Microsoft Outlook! Not much wrong at all, is there?
Read More
How to Fix Error Code 1309

What is Error Code 1309?

Error code 1309 is an error code that occurs when installing either Microsoft Office 2003 or Microsoft Office Project 2003. This error code may hamper your ability to run and use applications associated with Microsoft Office. To ensure installation is successful, it is first advisable to fix this error code. Error 1309 is displayed in any one of the two formats illustrated below. When installing Microsoft Office Project 2003, the error message may pop up as:
Error 1309. Error reading from file:    pathfilename.cab. Verify that the file exists and that you can access it.
When installing Microsoft Office 2003, the error message may appear in the following format: Fatal Error During Installation

Solution

Restoro box imageError Causes

Error code 1309 message may appear during Microsoft Office installation due to several reasons. These include:
  • Problems in the Oclncore.opc file. Project 2003 uses this version of the file for program installation.
  • Lack of adequate use permission
  • The requested file was not found
  • Setup registry entries are modified in an unacceptable manner
To avoid inconvenience and access Microsoft Office 2003 or Microsoft Office Project 2003, it is recommended to fix the error immediately.

Further Information and Manual Repair

To resolve this error you don’t need to be a technical whiz. Here are some of the best, easiest, and proven do-it-yourself methods to resolve error 1309 on your computer screen instantly.

Method 1 - Change CacheLevel Settings

If the problem is related to Oclncore.opc file then try changing CacheLevel settings. Follow these steps to work around this method.
  1. First, locate the PRJPRO*.XML file in the FILESSETUP folder of the Project 2003 installation source and then open this file in the Notepad.
  2. Also, make sure that you do not open the file as read-only and make sure that a checkmark is not displayed next to Word Wrap on the Format menu.
  3. The next step is to search the file for the following text string: OCLNCORE.OPC_1033.
  4. Now on the line where this string is located, change the CacheLevel=’1’ setting to the following CacheLevel=’3’ save the file back to the original location, and then quit Notepad.
After the changes are activated, try installing the software again on your system. If it installs successfully, then this means error 1309 is resolved. If the error still persists then try other given methods.

Method 2 - Configure security settings to get full permission

When the cause of error 1309 on your PC is related to lack of adequate permission issues, then configure security settings to resolve. To do this, simply locate the folder on your installation drive. Then right-click the folder and click Properties. On the Security tab, click edit and now make sure your user name is added to the list. Grant required security permissions and then click OK to save changes. After this, try installing Microsoft Office 2003 again on your system.

Method 3 - Copy the requested file from another source

If the error 1309 pops up because the requested file was not found, then try this method. Simply copy the file specified in the error to the destination directory. For example, if the error shows data1.cab was not found, then copy this file from another source and paste it into the directory specified in the error description.

Method 4- Remove bad registry entries

Bad registry entries are responsible for registry setup modification. If this is the reason for error code 1309, then download Restoro. This is a user-friendly PC Repair Tool embedded with a powerful registry cleaner. It scans and removes all bad and invalid entries accumulated in the registry. It cleans and repairs the registry resuming it back to its normal function. Click here to download Restoro and repair error 1309 today.
Read More
Delete Downloaded, Failed and Pending Windows Updates in Windows 10
There are instances when instead of fixing problems the Windows Update brings you problems on your Windows 10 computer. You might even see some pending Windows Updates which for some reason, refuse to install no matter what you do. The good thing is you won’t have to deal with those failed and pending updates that are incompletely downloaded to your PC as you can actually delete them. Follow the instructions prepared below to delete the failed and pending Windows Updates.

Step 1: The first thing you have to do is delete all the contents in the Temporary folder

  • Tap the Win + R keys to open the Run dialog box.
  • Next, type in “%temp%” in the field and hit Enter or click OK to open the Temporary folder.
  • From there, select all the folders and files within the Temporary folder and then delete them all.
Note: %temp% is one of the many environment variables in Windows that could open the designated folder by Windows as the Temporary folder which is usually located at C:\Users[username]AppDataLocalTemp.

Step 2: Next, remove the pending.xml file

  • Go to the C:\Windows WinSxS folder.
  • Once you’ve opened the folder, look for a file named “pending.xml” file and right-click on it and you can either rename it or delete it.
  • After that, the Windows Update should delete the pending tasks and build a fresh new update.

Step 3: Delete all the contents of the SoftwareDistribution folder

The Software Distribution folder in the Windows operating system is a folder that can be found in the Windows directory and is used to store files temporarily which might be required to install the Windows Update on your PC. Thus, it is required by the Windows Update and maintained by WUAgent. Aside from that, it also contains all the Windows Update History files and once you delete them, you will most likely lose the Update history. As a result, the next time you run the Windows Update, it may result in a longer detection time.
  • Open the WinX Menu.
  • From there, open Command Prompt as admin.
  • Then type in the following command – don’t forget to hit Enter right after typing each one of them.
net stop wuauserv net stop bits
  • After entering these commands, it will stop the Windows Update Service and the Background Intelligent Transfer Service.
  • Next, got to the C:\Windows\Software\Distribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.
  • Once all the contents in the Software Distribution folder are deleted, restart your PC and then go back to Command Prompt and input the following commands again.
net start wuauserv net start bits
Since the folder has already been flushed, it will be populated afresh the instant your restart your computer and open Windows Update.

Step 4: Try resetting the catroot2 folder

You can also try resetting the catroort2 folder as it is known to fix tons of Windows Update issues. Both the Catroot and catroot2 are Windows operating system folders that are required for the Windows update process.  So when you run the Windows Update, the catroort2 folders stores the signatures of the Windows Update package and helps it in the installation. It makes use of the “%windir%System32catroot2edb.log” file in the updating process. Afterward, the updates are stored in the SoftwareDistribution folder which is used then by the Automatic Updates in order to execute the updating process. Keep in mind that you must not rename or delete the Catroot folder. Although the Catroot2 folder is recreated automatically by Windows, the Catroot folder isn’t.
Read More
1 2 3 171
Logo
Copyright © 2023, ErrorTools. All Rights Reserved
Trademark: Microsoft Windows logos are registered trademarks of Microsoft. Disclaimer: ErrorTools.com is not affiliated with Microsoft, nor claims direct affiliation.
The information on this page is provided for information purposes only.
DMCA.com Protection Status