Disable Windows 11 animations for fast work

Microsoft’s initial Windows 11 hardware requirements were not really well received by users and they were not really clearly represented from the start making a lot of potential customers slowly drift away from the hype. It seems that Microsoft has acknowledged this since they have changed their tune about system hardware requirements for the upcoming Windows 11. It seems that Windows 11 will be able to be officially installed on unsupported computers but with a little inconvenience.

What is a catch?

Windows 11 will still have the same hardware requirements and if the PC meets them, that computer will be officially supported, other ones (any that can run Windows 10) that do not meet system requirements can still run Windows 11 but the system will have to be clean installed. So no upgrade option for old computer users, just a clean install. This means of course that you will need to download the ISO image and make a bootable USB in order to install it. Also since you will be doing a clean install do a backup of the hard drive since it will need to be formatted. Also, Microsoft has stated that with unofficially supported PC some driver updates might not be delivered leaving you with either older driver versions or relying on your hardware manufacturer on them. This is still not confirmed by Microsoft, just stated as an option. We will see how it goes.

Conclusion

It is very good that Microsoft has reconsidered its system requirements and will not stubbornly push its initiatives over the top requirements allowing even older computers to install new OS. I am sure over time lot of users will upgrade their hardware and drive into officially supported waters, but it is good that they will be able to use new OS on their current hardware.

If the Diagnostic Data level in your Windows 10 computer is configured manually to the non-default security setting of zero and you’ve encountered an error code of 0xc0000005, read on as this post will guide you in fixing the problem with the Remote Access Connection Manager Service. In relation to error 0xc0000005, you might also encounter an error in the Application section of Windows Logs in the Event Viewer, along with the Event ID 1000 which would most likely have a reference of “svchost.exe_RasMan” and “rasman.dll”. Before you troubleshoot the problem, keep in mind that the Remote Access Connection Manager or RasMan service is the one that manages dial-up and VPN connections from the computer to the internet as well as other remote networks. Each time you connect, the Services dials the connection or sends out a request for a VPN connection. However, the error 0xc0000005, only occurs when a VPN profile is configured as “Always On VPN or “AOVPN” connection with or without a device tunnel. There are several options you can check out to resolve this error, you can try to install the KB Update 4505903 or fix it via Group Policy. You could also try to enable Telemetry from the Settings app or enable it via Registry Editor. For more information, make sure to check out the provided options below.

Option 1 – Try installing the KB Update 4505903

The first thing you can do to fix the problem is to make sure that you’ve already installed the KB Update 4505903 in your computer. If not, then you have to go to Settings > Update & Security > Windows Update and from there select the Check for updates link. You need to get the standalone package if you are using the Microsoft Update Catalog to update your computer and for that, you have to the website of the Microsoft Update Catalog. On the other hand, if you are using the Windows Server Update Services or WSUS, then you can just manually import the KB Update 4505903 into WSUS.

Option 2 – Try to enable Telemetry in the Group Policy and run the RASMAN service

The next thing you can do to fix the problem is to enable Telemetry via Group Policy and then run the RASMAN service. To do that, follow these steps:

• Tap the Win + R keys to open the Run dialog box and type “gpedit.msc” in the field and hit Enter to open the Group Policy Editor.
• Next, navigate to Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds > Allow Telemetry.
• After that, open the policy and select one of the security levels like Basic, Enhanced, and Full.
• Then click on the Apply and OK buttons to save the changes made and close the Group Policy Editor.
• Once one, open the Run dialog box again and type “services.msc” in the field, and hit Enter to open the Windows Services Manager.
• From there, look for the Remote Access Connection Manager Service and restart it. And then check if it resolved the problem or not...

Option 3 – Try enabling Telemetry via Settings

• Tap the Win + I keys to open the Settings app.
• Next, go to Privacy > Diagnostics and Feedback and select Basic or Enhanced under the Diagnostic data.
• After that, tap the Win + R keys to launch Run and type “services.msc” in the field, and hit Enter to open the Services Manager.
• From there, look for the Remote Access Connection Manager Service and restart it.

Option 4 – Try to enable Telemetry via Registry Editor

• Launch the Run utility and type “regedit” in the field and tap Enter to open the Registry Editor.
• Then navigate to this path: HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsDataCollection
• From this path, look for “AllowTelemetry” and double click on it.
• Now enter the values, 1, 2, 3 for Basic, Enhanced, Full, respectively.
• If you can’t find AllowTelemetry, then just create a DWORD (32-bit) and name it “AllowTelemetry” and edit its value.
• Once done, exit the Registry Editor and restart the Remote Access Connection Manager Service from the Services Manager.

In case you don’t know, there is a built-in tool in Windows 10, known as Reliability Monitor that provides a day-to-day snapshot of the health of your system. It warns users of any looming issues or disasters before your computer breaks down finally. So obviously, Reliability Monitor is useful, however, there are times when it could behave incorrectly. For instance, it might fail to show you any updates even when they are installed. Thus, if you experience any malfunctions with the Reliability Monitor tool in Windows 10, read on as this post will guide you in updating or working in Windows 10. To fix the problem with the Reliability Monitor, there are several fixes you can check out. You can try to enable the data collection for Reliability Monitor or reset it, as well as put your computer in a Clean Boot State. For more information, refer to each one of the options given below.

Option 1 – Try to enable the Data Collection for Reliability Monitor

The Reliability Monitor tool uses data provided by the RAC Agent scheduled task and it will start to display a Stability Index rating and specific event information 24 hours after the system installation. The RACAgent scheduled task, by default, runs after the operating system is installed. And if it is disabled, it must be manually enabled from the Task Scheduler snap-in for MMC or Microsoft Management Console. Thus, you need to enable the Data Collection for Reliability Monitor to fix the problem.

Option 2 – Try to reset the Reliability Monitor

The next thing you can do to fix the issue with the Reliability Monitor might want to reset it to resolve the problem. If the Reliability Monitor is already open, you have to close it and open it again. After the reset is done, it may take up to 24 hours for the Reliability Monitor to display results again. This should fix the problem.

Option 3 – Troubleshot the problem in a Clean Boot State

There are some instances that some conflicting programs installed in your computer might be the one that’s causing the Black border issue. 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.

Installing Windows updates, installing a new driver from the manufacturer, or even just installing an application or game can cause sometimes certain components of your computer to stop working properly or introduce issues that were not present just before mentioned installation. Luckily for all of us, Microsoft seems aware of this potential issue and we have the option to roll back an older driver which performed well and had no issues at all. In order to do this first press ⊞ WINDOWS + X to open the hidden start menu and click on Device Manager. From the Device Manager choose the troublesome device and right-click on it, choose properties. Device properties floating Window will appear. Click on the top tab which says, Driver. From the Driver tab, click on Roll Back Driver. Note that if the device is working properly, the Roll Back Driver button will be greyed out and you will not be able to click on it meaning that chosen device is not the issue. If the device is not working properly and you can click on Roll Back driver, do it, choose the previous version, and reboot your computer. You can use this method to get back to the previous driver version for any device that is causing issues in your computer.

If you suddenly encountered an error that says, “The Task image is corrupt or has been tampered with”, along with an error code of 0x80041321, read on as this post will guide you on what you can do to resolve this problem in your Windows 10 computer. According to security experts, this kind of error has something to do with a corrupt scheduled backup task wherein each time the task service plans to execute a task, it validates a few things. And if it finds any issue with the integrity or corruption in the registry, it will mark those tasks as corrupt and throws the error 0x80041321. There are several options you can check out to fix the problem. You can try using the Registry Editor to edit and fix the corrupted tasks or you could also delete the schedule keys or the WindowsBackup file, as well as try deleting the task from the Task Scheduler or refresh the User_Feed_Synchronization. But before you of these potential fixes, make sure that you check every option and verify if it’s not associated or trying to run a file which it should not. In addition, make sure that you create a System Restore point as well so that you can undo any changes you will be making if anything goes wrong. Once you have these things covered, refer to each one of the options provided below.

Option 1 – Try to use the Registry Editor to edit and fix corrupted tasks

The first thing you can do to fix the problem is to edit those tasks via Registry Editor, as well as fix the corrupted ones in System32. Before you proceed, keep in mind that since you are dealing with the Backup triggered by the Task Scheduler, you can find the entries for the tasks in different locations. You can find the Task Scheduler at Task Scheduler Library > Microsoft > Windows > Windows Backup, whereas, you can find it in this path in the Registry Editor, HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows NT CurrentVersion Schedule WindowsBackup AutomaticBackup. On the other hand, you can find the Windows System folder at C:/Windows/System32/Tasks/MicrosoftWindows/WindowsBackup. You need to ensure that the name of the task name is the same as everywhere and take note of the name. Once you have these covered, follow the steps below.

• Tap the Win + R keys to open Run and type “Regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to this key: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTreeMicrosoftWindowsWindowsBackup
• From there, take note of the GUID value in the ID entry of the task under the AutomaticBackup and Windows Backup Monitor folder.
• After that, you have to remove the task registry entries related to the ID from these locations
  • HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCachePlain
  • HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheLogon
  • HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheBoot
• Once done, you have to create a temporary copy of the corrupted task file by going to this location: C:/Windows/System32/Tasks/MicrosoftWindows/WindowsBackup
• From there, look for the AutomaticBackup and Windows Backup Monitor tasks and copy them to a location where you can keep them safe.
• Next, you have to fix the corrupted task by deleting it from this location: C:/Windows/System32/Tasks/MicrosoftWindows/WindowsBackup
• After that, you have to recreate the task by going to Task Scheduler > Microsoft > Windows> Windows Backup.
• Now click on the Action menu and on Import task and navigate to the backup files and import them.
• Once you’ve created the tasks, run them manually and see if the error is now fixed.

Option 2 – Try to delete the Schedule keys in the Registry

• Launch the Registry Editor and go to this key: HKLMSOFTWAREMicrosoftWindows NTCurrent VersionSchedule
• From there, delete all of its sub-keys.
• Once done, exit the Registry Editor and check if the Backup Tasks are now working.

Option 3 – Try to remove the WindowsBackup file

The next thing you can do to fix the problem is to remove the WindowsBackup file if the first two options didn’t work. It is possible that the problem has something to do with corrupted Task files. The task files are XML files that include parameters, programs to use, and many more. If any of these files end up getting corrupted, the task scheduler will have trouble running it and will throw the “The Task image is corrupt or has been tampered with” error.

• To delete it, go to C:WindowsSystem32TasksMicrosoftWindowsWindowsBackup.
• From this location, get rid of all the files. You could also these files via Command Prompt using the DEL command.
• Once done, go to the Backup and Restore in the Control Panel and set up the Windows Backup again.

Option 4 – Try to delete the task from the Task Scheduler

If you don’t want to delete the files from Windows Explorer, you can delete them instead via Task Scheduler.

• Open the Task Scheduler and go to Task Schedule LibraryMicrosoftWindowsWindowsBackup.
• From there, delete both of the tasks and set up Windows Backup again.
• Once done, go to the Task Manager and run the AutomaticBackup task again and see if it works.

Option 5 – Try to restart the Task Scheduler service

As mentioned, it is possible that the Task Scheduler service could be disabled. You could have disabled it when trying to enhance your computer’s performance and whatnot. Thus, you need to verify if it’s running or not and then restart it.

• First, you need to tap the Win + R keys on your keyboard to open the Run dialog box.
• Next, type “services.msc” in the field and click OK or tap Enter to open the Windows Services Manager.
• You will see a list of Services and from there, look for the Task Scheduler service and double click on it.
• After that, go to the General tab and click on the Startup Type options and then select “Automatically” from the given list.
• Click on the “RUN” option and select the “Restart the Service” option.
• And click on the “After Second Failure” option and then select the “Restart-Service” option again.
• Now click on the “After Subsequent Failures” tab and select the “Restart the Service” option.
• Finally, click on the Apply and OK buttons and then run the Task Scheduler and see if the issue is now fixed.

Option 6 – Try refreshing the User_Feed_Synchronization

According to security experts, enabling and disabling the User Feed sync also known as the User_Feed_Synchronization task can help resolve the problem.

• Tap the Win + X keys and select the PowerShell (admin) option from the menu.
• Next, type the “msfeedssync disable” command and tap Enter.
• Repeat the same process but this time run the “msfeedssync enable” command.

If you are using Google Chrome browser in surfing the web, you might have experienced a situation where you’re trying to connect to a website but were unable to since Chrome failed to fetch the website to the browser and throws an error that says, This webpage is not available – Err Connection Timed Out. Aside from an issue with the network connection, there are also other reasons why this error suddenly shows up, read on to fix it. There are times when the Windows computer is responsible for this kind of issue. And it can happen not just to Google Chrome but to other browsers as well. To resolve this issue, here are some suggestions that might be of help.

Option 1 – Try checking the network cables and then restart your router and reconnect

The first thing you can do is to check if all the network cables are properly connected be it to your computer or to the router. And if your computer is connected via Wi-Fi, you need to restart your router once. And of course, you can always opt to forget the Wi-Fi details and then reconnect again just make sure that you know the password.

Option 2 – Check the Windows Host file

You can also try to cross-check the Windows Hosts file to find out if the website you are trying to open has been blocked because if it is, then it’s no wonder why you’re getting the ERR CONNECTION TIMED OUT error in Chrome. There are instances when some third-party application modifies the file and adds some websites to the blocklists. So if the website is indeed blocked, you need to remove it from the list.

Option 3 – Try removing Proxy

Removing the Proxy might also help you in fixing the ERR CONNECTION TIMED OUT error. Here’s how you can do it:

• Tap the Win + R keys to open the Run dialog box.
• Then type “inetcpl.cpl” in the field and hit Enter to pull up the Internet Properties.
• After that, go to the Connections tab and select the LAN settings.
• From there. Uncheck the “Use a Proxy Server” option for your LAN and then make sure that the “Automatically detect settings” option is checked.
• Now click the OK and the Apply buttons.
• Restart your PC.

Note: If you are using a third-party proxy service, you have to disable it.

Option 4 – Try to clear the browsing data of Google Chrome

If your browsing data in Chrome hasn’t been cleared for some time now then that might be the reason why you’re suddenly getting the ERR CONNECTION TIMED OUT error when you browse the web. To fix this error, you need to clear your web browsing data. Refer to the following steps to do so.

• Tap the Ctrl + Shift + Delete buttons to go to the Clear browsing data section in Chrome.
• Next, set the time range to “All time” and tick all the boxes and then click on the Clear data button.
• After that, restart the Chrome browser and try to open the website you were trying to open earlier.

Option 5 – Flush the DNS and reset TCP/IP

You might also want to flush the DNS and reset TCP/IP as it could help in fixing the ERR CONNECTION TIMED OUT error. To do so, refer to these steps:

• Click the Start button and type in “command prompt” in the field.
• From the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
• After opening Command Prompt, you have to type each one of the commands listed below. Just make sure that after you type each command, you hit Enter
  • ipconfig /release
  • ipconfig /all
  • ipconfig /flushdns
  • ipconfig /renew
  • netsh int ip set dns
  • netsh winsock reset

After you key in the commands listed above, the DNS cache will be flushed and the Winsock, as well as the TCP/IP, will reset.

• Now restart your computer and open Google Chrome then try opening the website you were trying to open earlier.

Option 6 – Run the built-in Malware Scanner and Cleanup Tool in Chrome

In case you don’t know, there is actually a built-in malware scanner and cleanup tool in Chrome that helps you get rid of any unwanted ads, pop-ups, and even malware, as well as unusual startup pages, toolbars, and other things that could affect the performance of the browser.

Option 7 – Reset Chrome

Resetting Chrome can also help you get rid of the ERR CONNECTION TIMED OUT error. Resetting Chrome means restoring its default settings, disabling all the extensions, add-ons, and themes. Aside from that, the content settings will be reset as well and the cookies, cache, and site data will also be deleted. To reset Chrome, here’s what you have to do:

• Open Google Chrome, then tap the Alt + F keys.
• After that, click on Settings.
• Next, scroll down until you see the Advanced option, once you see it, click on it.
• After clicking the Advanced option, go to the “Restore and clean up the option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
• Now restart Google Chrome.

If Error Code 0xc00000e9 appears on your screen, there is no cause to panic yet as there are different ways to fix this. Here, I will list down different methods to get your computer back on track:

1. Check peripheral connections
2. Check your SATA cables
3. Check your hard drive
4. Check your BIOS settings

Quick Fix 1. Check Peripheral Connections

1. Turn off your computer.
2. After the computer has been shut down, take off all the peripherals or the USB cables that are connected to your USB ports. This includes even the keyboard and the mouse. We just need to have only the monitor plugged in for this one.
3. Turn on your computer and see if it starts as it normally does.
4. If it does, try connecting back your external devices or peripherals one by one until you find the one that causes the error.
5. Once you trace the device that’s causing the error, you will have to change its USB cable and update its driver to support your operating system.

Quick Fix 2. Check your SATA cables

It is possible that what causes a barrier between your operating system and your hard drive from communicating is the SATA cable used. For example, if you’re using an older SATA with a SATA III port, there might not be adequate support for the transfer of data from one another. Or, the problem might be a loose SATA cable which would still require you to buy a new one to replace your loose or damaged cable. To check if your SATA cables are causing the error, simply follow these steps:

1. Turn off your computer.
2. Carefully open its case.
3. Check the hard drive and the SATA port where it’s connected.
4. Try to use a newer cable and connect it to your SATA port. (If you used a SATA II cable, you can see if a SATA III cable is more compatible.)
5. Replace your SATA cable with a newer one if Step 4 proves to be successful.

Quick Fix 3. Check your hard drive.

1. Try to use a different hard drive and see if error code 0xc00000e9 still appears.
2. If it works out just fine, then the problem might be physical damage to your hard drive and would need to be repaired depending on the case. Just simply take it to a technician and let him know about the issue.

Quick Fix 4. Check your BIOS settings

1. Restart your computer.
2. Once your computer starts, press and hold the ESC, F2, F12, or DEL key to go to BIOS settings.
3. You will then be redirected to the BIOS Setup Utility screen. From here, go to Boot options.
4. In the Boot Options, see if your first boot device is your hard drive. If it isn’t, press the arrow key to select the hard drive and move it to the top of the boot device list.
5. Save the settings.
6. Reboot your computer.

Note: If all the methods above do not work, the problem might be on your drivers and you might need to update them. You can update your driver in two ways: Manual driver update and Automatic driver update. You can find procedures online in updating your drivers.

Driver Verifier is a built-in tool in Windows 10 that monitors device drivers on your computer, if it detects issues with drivers, it will attempt to fix the issue. If you are encountering Blue Screen for a Driver and after running Driver Verifier you get another with message DRIVER_VERIFIER_DETECTED_VIOLATION ten follow this article step by step in order to solve it. There is a chance that you will maybe even have to do this in safe mode, if that is your case, login into safe mode and proceed, otherwise proceed normally.

1. Update Device Drivers

   the most common issue with the blue screen is old Drivers, in most cases, graphical drivers, update all Drivers with the latest versions and see if this will resolve the issue.

2. Stop or uninstall Virtualization software

   Virtua machine software is a great way to have a safe environment and to experiment while preserving your Windows installation intact, however sometimes due to the nature of these applications they can be a case for blue screen errors. Stop virtualization software to see if it will remove the issue. If that is the case, try another virtualization application

3. Disable Driver Verifier

   Press ⊞ WINDOWS + X to open the secret menu Click on Command Prompt (admin) Inside command prompt type: verifier and press ENTER Select the Delete existing settings radio button Click Finish Reboot your computer

4. Reset Driver Verifier

   Press ⊞ WINDOWS + X to open the secret menu Click on Command Prompt (admin) Inside command prompt type: verifier /reset and press ENTER Reboot your computer

5. Use system restore

   Rollback Windows to the previous state where everything was working fine.

Internal Error 2753 - What is it?

Internal error 2753 is associated with Windows Installer failure. The Windows Installer is basically an in-built software program in Windows 7 and 8. It installs all programs on the system smoothly, saves the program in the computer program files and in the Windows Registry. Though this can be carried manually Windows Installer makes the installation process much easier. However, internal error 2753 can cause a great deal of distress and frustration during program installation. This error prevents you from installing your desired program successfully.

Solution

Error Causes

The 2 known causes for Internal Error 2753 are:

• Viral infection
• Windows Installer not properly registered

Further Information and Manual Repair

To resolve internal error 2753 on your system, try the methods discussed below. These methods are easy and require no technical expertise. Let’s get started:

Method 1 - Remove All Malicious Programs

Malicious programs like viruses, malware, adware, Trojan and spyware can corrupt programs on your PC like Windows Installer. If this is the underlying cause of error code 2753, then simply download a powerful antivirus on your system. Run it to scan for all such malicious programs and remove them. Once your PC is clean, try installing your desired program. This will hopefully resolve the issue. If the error still pops up then try method 2.

Method 2 - Register Windows Installer Properly

To do this, go to the start menu and then open Run and type ‘cmd’ in the box, and press OK. This will open the DOS command window. In the command prompt type "regsvr32 vbscript.dll" and then press Enter to proceed. After that, you will see a message that will read as "DllRegisterServer in vbscript.dll succeeded." This means Window Installer files have been successfully registered on your PC.  Now you can try installing your desired program again. If the installation begins and completes successfully, then the error is resolved.

Method 3 - Undo Recent Changes

If nothing works, then use the Windows System Restore Utility tool to undo recent changes. This will bring back your PC in the former state before you experienced the error 2753 on your PC. To access System Restore Utility, press Start and type System Restore in the search box. Now follow the steps in the Wizard to choose a restore point. Once you select the point, reboot your system to activate changes.

Error Code 0x8007007e – What is it?

Error code 0x8007007e occurs in Windows 8 or 8.1 when users attempt to, but fail to successfully use Windows Update. When this occurs, Windows 8 or 8.1 users will not be able to access updates or certain web pages. This error manifests itself via the following common symptoms:

• Inability to complete tasks via Windows Update
• Message box displaying error code 0x8007007e message

Solution

Error Causes

Error code 0x8007007e is usually caused by a malfunction within your system. This malfunction may be due to several issues such as malware on your device, or the accidental removal of a registry entry or system file.

Further Information and Manual Repair

To correct issues related to error code 0x8007007e in Windows 8.1, users may need to employ one or several manual repair methods. Users will not necessarily need technical skills to accomplish this task. However, if you are uncertain of your skills or you are unable to resolve the issue after completing the tasks below, consult a Windows repair technician or use an automated tool.

Method one: System File Checker

System File Checker (SFC) enables users to check their system for corrupt or missing system files. You will need to use Command Prompt. To access System File Checker on Windows 8 or 8.1, follow the instructions below.

• Step one: Tap or use the mouse to click Search
• Step two: Type Command Prompt in the Search box
• Step three: Select Command Prompt, and then click Run as administrator
• Step four: Type password if prompted by Command Prompt to do so or simply click Allow

Whether you run Windows 8 or 8.1 operating system on your computer, System File Checker will begin to find and repair missing or corrupted system files. If, however, you are unable to successfully complete the task via Command Prompt, repeat the steps above. You may also consider help from a professional or simply move to the next manual repair method listed below.

Method two: Perform a Clean Boot

A Clean Boot will help users determine if error code 0x8007007e in Windows 8.1 is caused by a problem associated with startup programs. Problems may arise when there is conflict among programs that run in the background when users turn on their device. To run a clean boot, follow the steps below:

• Step one: Click the Start button and type msconfig in the search box
• Step two: Click Services tab
• Step three: Click Hide all Microsoft Services box then select Disable All
• Step four: Click Startup tab
• Step five: Select Disable All, then OK
• Step six: Restart the computer then check if you can now update the system

If the Clean Boot is successful, you will be able to successfully update your system without receiving error code 0x8007007e. However, if the error code reappears while you attempt to access updates or web pages, proceed to the next manual repair method below.

Method three: Scan for Malware

Since error code 0x8007007e in Windows 8 or 8.1 can be caused by issues related to malware, it’s important for users to check their system using a powerful antivirus or anti-malware software. If you do not have one on your system, you will need to download such software as soon as possible.

Once you have the software on your PC, run a scan to check if your computer has been infected. If malware is indeed on your device, remove it using the anti-malware tool.

Method four: Run System Restore Tool

Another effective manual repair method relates to System Restore. This tool enables Windows users to restore their computer to an earlier period of time in which the error code was not present. When done properly, it can effectively resolve error code 0x8007007e. Before running this tool, however, be sure you select a time in which all important files and programs are present so as not to lose them.

Method Five: Use an Automated Tool

If you wish to always have at your disposal a utility tool to fix these Windows 8 and other related issues when they do arise, download and install a powerful automated tool.