Stop the Hotspot from Turning off

The third time is charm saying goes but not when we are talking about Microsoft. Print spooler is again in focus, in a bad way. This is the third print spooler vulnerability to emerge in just five weeks. While a critical flaw was originally identified and patched in June, a similar flaw came to light shortly after and was subsequently patched (with mixed success). Microsoft is once again advising its customers to disable Windows print spooler after a new vulnerability that allows hackers to execute malicious code on machines has emerged. While a patch fixing the flaw will be released in due course, the most effective workaround currently on the table is to stop and disable the print spooler service entirely.

"An elevation of privilege vulnerability exists when the Windows Print Spooler service improperly performs privileged file operations. An attacker who successfully exploited this vulnerability could run arbitrary code with SYSTEM privileges. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights."

Stop this service right away or you are risking a potential attack.

1. Press ⊞ WINDOWS + X to open the hidden menu
2. Click on Power Shell (admin)
3. In Power Shell type in the following command to check if spool service is running: Get-Service -Name Spooler followed by ENTER
4. If spooler service is running type in the next command to stop it: Stop-Service -Name Spooler –Force and press ENTER
5. Then follow with this command to disable it at startup: Set-Service -Name Spooler -StartupType Disabled followed with ENTER

That’s it, we hope a patch will come soon for all the people that are using network printing and indeed need this service running in order to do work.

If you suddenly encountered the PDC WATCHDOG TIMEOUT BSOD Blue Screen stop error with a bug check value of 0x0000014F, then it’s probably due to a system component that has failed to respond with the allocated period which prevents the system from exiting connected standby. This kind of Blue Screen error could be caused by both hardware and software components. To fix this Stop error, here are some possible fixes you can try that might help but before you proceed, make sure that you create a System Restore point first and boot your computer into Safe Mode with Networking.

Option 1 – Try to rollback, update or disable drivers

The next thing you can do to fix the PDC_WATCHDOG_TIMEOUT Stop error is to roll back, or update, or disable device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• After opening the Device Manager, look for the device driver named “IDE ATA/ATAPI controllers” and expand it.
• Then look for the SATA AHCI Controller entry and right-click on it. If you haven’t updated this driver in a while, select the “Update Driver” option. On the other hand, if you’ve just updated this driver, then select the Uninstall Device option.
• Next, follow the screen option to update or uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically if you have chosen to uninstall them.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 2 – Try to disconnect or disable newly installed hardware

In this option, you will have to disable or remove the hardware you’ve just installed recently since external devices could be the one that’s causing the Blue Screen of Death error to appear. To do that, just disconnect any external device that’s connected to your computer physically and then check if it fixes the PDC_WATCHDOG_TIMEOUT Blue Screen error.

Option 3 – Try running the Memory Diagnostic Tool

The Memory Diagnostic tool in windows can help resolve the PDC_WATCHDOG_TIMEOUT Blue Screen error by checking and automatically fixing any memory-based issues. To run it, refer to these steps:

• Tap the Win + R keys to open Run and type mdsched.exe and hit Enter to open the Windows Memory Diagnostic Tool.
• After that, it will give two options such as:
  • Restart now and check for problems (Recommended)
  • Check for problems the next time I start my computer
• Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Option 4 – Try to update the BIOS

Updating the BIOS can help you fix the PDC_WATCHDOG_TIMEOUT BSOD error but as you know, BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “msinfo32” in the field and press Enter to open System Information.
• From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
• After that, you should see the developer and version of the BIOS installed on your PC.
• Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
• If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
• Now double click on the downloaded file and install the new BIOS version on your computer.
• Now restart your computer to apply the changes made.

Option 5 – Try running the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like PDC_WATCHDOG_TIMEOUT. It can be found in 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.

There are times when after you upgrade your Windows operating system, the System Logs under the Event Viewer will display an error message saying, “Event ID 10010 error – The server did not register with DCOM within the required timeout”. What is DCOM? DCOM stands for “Distributed Component Object Model”. It is a proprietary Microsoft technology that allows the Component Object Model or COM software to communicate across a network. You can consider it as an extension of COM which is equipped with the capability of solving a couple of inherent problems related to the COM model to the better use over a network. COM is a tool that’s used for advanced configuration and troubleshooting in Windows 10. Developers usually use it to configure routine components and application behavior like participation in transactions and object pooling and so on. The Component Services needs the DCOM wire protocol in order to communicate with the Component Object Model components on other computers. By default, in a Windows-based system, the network computers are configured initially to enable DCOM. There are also some components in Windows that might require registering themselves with DCOM. However, if they fail to do so, you will encounter the “The server did not register with DCOM within the required timeout” error. To fix this, here are some suggestions you can check out.

Option 1 – Try to use the Component Services

• Tap the Win + R keys to open the Run dialog box.
• Then type “dcomcnfg” in the field and tap Enter to pull up Component Services.
• Next, double click on the Computers folder located in the right pane and right-click on My Computer, and select the Properties option.
• After that, switch to the COM Security tab under My Computer Properties and then go to the Access Permissions section.
• From there, click the Edit Default button and in the new window that appears, apply the correct permission to objects under the Group or user names section.
• Once you’re done, click OK and exit. This should fix the error.

Option 2 – Make sure that Function Discovery Resource Publication Properties Services is running

• In the Cortana search box, type “services” and click on the Services icon to open the Services Manager. Alternatively, you can also tap the Win + R keys to launch the Run prompt and then type “services.msc” in the field and hit Enter to open the Services Manager.
• Next, scroll down and look for the “Function Discovery Resource Publication” entry and double click on it.
• Then switch to the General tab and from there, make sure that the Startup Type is set to “Manual (Triggered).
• You also have to make sure that the service is running so if it’s not, just click on the Start button to start the service.
• Now click on Apply to save the changes made.

Option 3 – Try resetting the default DCOM permissions

• Tap the Win + R keys to open the Run dialog box.
• Then type “dcomcnfg” in the field and tap Enter to pull up Component Services.
• After that, expand Component Services > Computers and right-click on My Computer, and then select Properties.
• Next, go to the Default Properties tab, and in the Default Distributed COM Communication Properties section, make sure that:
  • Default Authentication Level is set to Connect
  • Default Impersonation Level is set to Identify.

If you are using File Explorer but suddenly encountered an error saying, “No such interface supported”, read on as this post will guide you on how to fix the problem. This kind of error occurs due to the corruption in the system files which supports several tasks in the system that works with the Windows File Explorer process or File Explorer. This kind of error can give you a hard time in browsing the files on your computer, or when you open important utilities like the Control Panel, or when you copy files and other inconveniences. Needless to say, it won’t bring you any productivity at all and can only leave you frustrated. To fix this problem, there are several options you can try. You can try to run the System File Checker scan or the DISM tool. You could also try to re-register the potentially corrupted DLL files or fix the User Profile. For more details, refer to each one of the given options below.

Option 1 – Try to run System File Checker

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files that might be the cause why you’re getting the errors 0x8024a11a and 0x8024a112. To run the SFC command, follow the steps given below.

• Type “cmd” in the Start search and then right-click on the appropriate search result.
• Next, select “Run as administrator” to open Command Prompt with admin privileges.
• 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.

• Now restart your computer and see if the problem is fixed or not.

Option 2 – Try to fix the User Profile

The next thing you can do to fix the problem is to fix the User Profile. All you have to do is migrate to a new User Profile in Windows 10 by creating a new User Account and migrating all your personal files from the current user profile folder in the C:/Users location to the new user profile folder which is also located in the same folder.

Option 3 – Run the DISM tool

You can try running the Deployment Imaging and Servicing Management or DISM tool to fix the “No such interface supported” error. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt with admin privileges.
• Then type in the following commands and make sure to hit Enter right after you type each one of them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • exe /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. Once it’s done, restart your computer.

Option 4 – Try to re-register the problematic DLL file

You may have to re-register the ntdll.dll file using the regsvr32.exe before you can successfully install the program and fix the error. The Regsvr32 tool is a command-line utility that can be used to register and unregister OLE controls like DLL and ActiveX (OCX) controls in the Windows operating system. Follow the steps below to use it.

• Open Command Prompt as admin from the WinX menu.
• Next, type the following command in the elevated Command Prompt and hit Enter to execute it. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.

regsvr32 c:windowssystem32actxprxy.dll

• After you execute the given command, you should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. If it didn’t work, you can try to execute this command instead: FOR /R C: %G IN (*.dll) DO "%systemroot%system32regsvr32.exe" /s "%G"
• Once it’s done, restart your computer.

D3dx9_32.dll Error - What is it?

D3dx9_32.dll is basically a type of dynamic link library used to load and run different programs on the PC. The D3dx9_32.dll error message pops on the screen when this file is unable to load successfully. The error message is displayed in either of the following formats on the computer screen:

"The file d3dx9_32.dll is missing" "D3DX9_32.DLL is missing. Replace D3DX9_32.DLL and try again." "File d3dx9_32.dll not found" "D3dx9_32.dll not found. Reinstalling might help fix this." "Missing component d3dx9_32.dll"

This error usually pops while using gaming software. The D3dx9_32.dll error is displayed after a game is loaded or before the game-play begins. However, it may also appear in software that uses advanced graphic features.

Solution

Error Causes

D3dx9_32.dll error may occur due to multiple causes. These include:

• The problem is related to Microsoft DirectX software. This software includes the D3dx9_32.dll file in its software collection.
• Incompatible Video Card Drivers
• Improper game installation
• DLL File Corruption
• Registry issues
• Viral infection

Further Information and Manual Repair

To avoid inconvenience, it is advisable to fix the error right away. To resolve it you don’t need to be a technical whiz or hire a technician. Luckily, the D3dx9_32.dll file error is quite easy to fix. Here are some of the best and effective DIY methods that you can try to remove the error:

Method 1 - Install the Latest Version of DirectX

Since D3dx9_32.dll error is related to DirectX software, it is advisable to make sure that you have the latest version of this software installed on your PC. To install the updated version, simply go to Microsoft’s official website, download the software from there and install it on your PC. To activate changes, restart your computer.

Method 2 - Uninstall and then Re-install Gaming Application

If the error still persists, then the reason for it could be the gaming application. Sometimes D3dx9_32.dll error may also occur due to poor program installation. Therefore, in this case it is recommended that you first uninstall the program by going to the Add/Remove program option. And once the program is uninstalled, try re-installing it on your PC. Hopefully, it will remove the error.

Method 3 - Restore the Damaged/Corrupt D3dx9_32.dll File

The error may also pop due to the damaged or corrupt D3dx9_32.dll file. This indicated registry issues. When the registry becomes overloaded with unnecessary and obsolete files, there is not enough space for other files to store. Due to the poor registry maintenance, the system and dll files are often damaged. To restore the damaged D3dx9_32.dll file, you need to clean the registry first. You can do this manually, but that will be quite time-consuming and slightly technical. Therefore, download a registry cleaner. A registry cleaner scans all registry-related errors and removes them right away. It cleans the registry and restores the damaged dll files.

Method 4 - Scan for Viruses

If the D3dx9_32.dll error is triggered by viruses, then it is advisable to scan your PC with an antivirus. It will scan and removes all viruses from your system. Whether D3dx9_32.dll error is related to registry issues or viral infection, download Restoro. It is a cutting-edge, advanced, and multi-functional PC Fixer. A one-stop solution for all PC-related issues. It is deployed with a powerful registry cleaner, an antivirus, a system optimizer and several other scanners. The registry cleaner detects and removes all registry errors and repairs damaged Dll files including D3dx9_32.dll file and simultaneously the antivirus utility scans your entire PC for all types of malicious software infecting your system including spyware, Trojans, adware and malware. The system optimizer feature ensures your PC works at its optimal level. Restoro PC Fixer is safe and efficient. It has a user-friendly interface which makes it quite easy for all levels of users to operate. In just a few simple clicks, errors are resolved. In addition to this, you can download it on all Windows PC. It is compatible with all Windows versions. Click here to download Restoro and resolve D3dx9_32.dll error code on your PC today.

In 27 European countries for some time it has been considered for introducing a law that would force phones, tablets, laptops, and other mobile devices to use a single USB Type-C connector.

The European Parlament announced that a provisional agreement has been reached and that it was voted that a single charging solution is USB Type-C. The current agreement applies and covers the next devices: phones, tablets, Readers, earbuds, digital cameras, headphones, headsets, handheld consoles, and portable speakers. All currently existing devices can still be sold without issues but starting in the fall of 2024 all-new products must support USB Type-C charging.

The agreement will also hit Laptops but not on the same date, How is USB Type-C currently not enough for charging laptops, all new laptops that will have to use it are scheduled for fall of 2025.

Although the agreement is reached the EU Parliament and Council still have to formally approve everything.

Apple targeted the most

Apple has been targeted as the main target for rules since their iPhones are still using Apple's proprietary Lightning charging port. Apple sells a lot of iPhones in Europe and even though iPad Pro and iPad Air along with all MacBooks have moved to USB Type-C, iPhones are still struggling with the Lightning port.

Apple criticized the EU’s charger rules when they were first proposed in 2021, telling the BBC, “We remain concerned that strict regulation mandating just one type of connector stifles innovation rather than encouraging it, which in turn will harm consumers in Europe and around the world.” The European Union has said in response that it will update its rules as new technology arrives.

Why was this proposed?

The main problem in Europe that led to this proposition was electronic waste which reached 11 000 metric tons in 2018. European union is afraid that this will keep rising as chargers become larger and heavier in order to accommodate faster-charging speeds. More electronic waste means more hardware slowly decomposing in landfills that will contribute to climate change affecting everyone on the planet, not just the people living in Europe.

Error Code 0x801901F7 – What is it?

Error code 0x801901F7, also known as “The Server Stumbled” error because it shows a message saying “The Server Stumbled. We all have bad days” is associated with Windows Store. Server Stumbled Error 0x801901F7 is an error related to the MS server. The error occurs due to damaged registry files, malware, virus, and corrupted data. You should fix this error to prevent a system crash or a BSOD error. There are some things you can do to fix it. These are not so complex. So, anyone can try these methods to fix error 0x801901F7. Common Symptoms for error 0x801901F7:

• Problems with Windows startup
• System becomes very slow or the system freezes
• Blue screen of death appears
• Windows fails to start some process due to Stop error code 0x801901f7

Solution

Error Causes

• This error is generally caused by corrupt registry files.
• Virus infection can cause this problem.
• Outdated driver, missing .DLL files may also cause this error.
• Microsoft server overload may cause this problem as well.
• Incorrect configuration may cause this problem.

Further Information and Manual Repair

To fix error 0x801901f7, there are four methods listed below. Some might work for you and some might not. Please try all of them to fix this error.

Method 1:

Basic method to fix error code 0x801901F7: Resetting Windows Store Cache Most of the time clearing or resetting the cache helps. It doesn't always work, but you should try this first before moving on to some advanced methods which are mentioned below. To reset the Windows Store cache please follow the simple steps below

• Open RUN by searching or pressing "Windows Key + R"
• Type "wsreset.exe" and press Enter or click on OK.
• Windows Store will open automatically along with a command prompt.
• This will reset Windows Store and you might see it loading as it should.

This method might work but if it fails to solve Error 0x801901F7 then follow the method below.

Method 2:

Advanced method of fixing error code 0x801901F7: Deleting Windows Store database file. By using this method, you will be deleting the database file for Windows Store. This file is located on your C drive or the drive where you installed your Operating System. Follow the steps below.

1. Navigate to C:WindowsSoftwareDistributionDataStoreDataStore.edb.
2. Delete DataStore.edb file from there.
3. Now Open Windows Store and see if you still get error code 0x801901F7.

The Datastore.edb file that you deleted will be automatically created once you perform Step 3 which is launching Windows Store. If you still cannot get this error away then Close Windows Store and Reboot your PC then Launch Windows Store Again.

Method 3:

Modifying Windows update properties: Perform the steps below only if the above-mentioned methods fail. You will be tweaking a few things in the Windows update to see if it helps.

1. Open Task Manager by right-clicking on Taskbar, then click on Task Manager.
2. Go to Services Tab. Click on Open Services at the very bottom of the Window.
3. Now a new window will pop up. Scroll down & find "Windows Update" from the list.
4. Double click on Windows update to open up its Properties.
5. Now from the Startup Type drop-down list, select Automatic. Click on Apply, Start, and then Ok.

Now you need to perform just one more step. Reset Windows Store again (Refer to method 1 for Steps). This should fix your Windows Store error that shows The Server Stumbled with 0x801901F7 Error Code.

Method 4: 

If the error is due to a problem with a driver, then follow the method below to uninstall the current driver:

1. Open the Run command and type “sysdm.cpl” in the text box.
2. Click Enter.
3. Open the Hardware tab on the system properties dialog box.
4. Then press on Device Manager.
5. Double press on Device type and then press on the hardware device that is reporting error code 0x801901F7.
6. Go to the Driver tab and press on Uninstall button to uninstall the device driver completely.
7. Now, install the new driver on your computer.
8. Restart your computer.
9. Run virus scan of your PC
10. Try using a different USB port.

If you do not possess the technical expertise required to accomplish this yourself or do not feel comfortable doing so, download and install a powerful automated tool to get the job done.

If you suddenly encountered a Windows Error Code 0x80070017 during an Update, Installation or System Restore then it’s probably due to some missing or corrupted system files. This kind of error code can occur during an update, installation, or system restore and the only way out of it is to download the file once again and re-run the installation from the top. Before you start to troubleshoot the problem, you need to create a System Restore Point first. After you create a System Restore point, you can follow the troubleshooting options laid out below to fix the Windows Error Code 0x80070017. You just have to follow the troubleshooting option that applies to your situation and whether you got the error during an update, installation, or during System Restore. Whether you got the error 0x80070017 while updating Windows 10 or installing it or during a system restore, the first thing you must do is run the System File Checker. As pointed out early on, the Windows Error Code 0x80070017 might be caused by corrupted or missing system files so the first thing you can try is to run the System File Checker scan.

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

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.

If you have encountered Windows Error Code 0x80070017 during an Update, then here are some options you need to try:

Option 1 – Delete the files/contents in 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. A lot of users tried deleting the files in this folder to fix the problem and so far it has worked. Like them, you can try clearing the Windows Update cache by simply deleting the contents of the folder named “SoftwareDistribution” since Windows apparently can’t clear and re-download the update contents once they are corrupted. Thus, deleting the contents of this folder will make Windows download the contents again which will fix the problem. To do that, follow the steps below.

• 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, go to the C:/Windows/SoftwareDistribution 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.

Option 2 – Run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update Error Code 0x80070017. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go. On the other hand, if you got the error code 0x80070017 during a Windows 10 installation, then it’s because of bad media or corruption in ISO. Here are some troubleshooting steps for this kind of situation:

Option a – Try to create Windows 10 ISO media again

In this option, you will have to create a Windows 10 bootable media and use it to install the latest Windows 10 version. Most users reported that this option works and the reason why it does have something to do with the Windows Update client since the Windows Updates downloaded from the regular Windows Update client seem to create issues such as the error 0x80070017. However, issues like this one don’t occur when the very same Windows Updates are downloaded and installed via an ISO file. Take note that when using a Windows ISO file, you will be asked to choose what you want to do with the previous settings and apps. A lot of users opted for the “Not to keep the old Windows settings” option which has resolved the issue. So if you want to keep the previous settings then you must try to update Windows first while keeping the old settings. However, if it doesn’t work, you have to try installing the latest version of Windows without keeping the previous settings.

• Click this link and then click the Download Tool Now button.
• Next, click the “Use the tool to create installation media (USB flash drive, DVD, or ISO file)…” option and follow the next given instructions on the screen.
• Now select the ISO file option in step 5.
• After that, you should now have an ISO file.
• Next, go to the location where you’ve downloaded the ISO file.
• Then right-click on the Windows 10 ISO file and select the Open with the option and then select File Explorer.
• Now click on “setup.exe” and follow the next instructions that appear on the screen. When asked, you have to select either Nothing (clean install) or Keep personal files only option. Take note that you must not select the “Keep personal files, apps, and Windows settings since it doesn’t really work.

Option b – Run Microsoft’s online troubleshooter

Running Microsoft’s online troubleshooter might also help you fix the Windows update error 0x80070017. This online troubleshooter is known to help in fixing Windows Update errors, it scans your computer for issues that might be causing the problem and then fixes them automatically. If you got the error during System Restore then this means that the files that are being copied from the disk are not making it to the hard drive. To resolve it, here’s what you can do:

Option 1 – Run System Restore in Safe Mode

You might want to run System Restore in Safe Mode and see if it works. Just reboot your PC into Safe Mode and then run System Restore.

Option 2 – Reset Repository

• Boot your PC into Safe Mode.
• Then open Command Prompt as admin.
• Next, type the “net stop winmgmt” command and hit Enter to stop the Windows Management Instrumentation Service.
• After that, go to C:/Windows/System32/wbem. From there, rename the repository folder to “repository-old”.
• Restart your computer.
• After your computer has restarted, open Command Prompt as admin again and then type the “net stop winmgmt” command and hit Enter.
• Next, type the “winmgmt /resetRepository” and hit Enter to reset Repository.
• Restart PC and check if System Restore now works.

Option 3 – Try resetting Windows 10

To fix the error 0x80070017, you can try resetting Windows 10. Doing so won’t get rid of any file in your system – instead of erasing all your media files and documents, it only resets all the system settings and files. Simply go to Settings > Recovery. From there click the Get started button under the Reset This PC section.

We couldn’t update system reserved partition” - What is it?

Customers will most likely encounter the “We couldn’t update system reserved partition” error when upgrading to Windows 10 from Windows 7 or Windows 8.1. This error may also come with error code 0xc1900104 or error code 0x800f0922.

Solution

Error Cause

“We couldn’t update system reserved partition” Windows 10 upgrade error is normally caused by too little space on the System Reserved Partition (SRP). The System Reserve Partition is an additional small partition created by Windows, which stores boot files. The SRP can be filled up with security apps and third-party anti-virus. Once this partition has insufficient space, the system will not be able to upgrade to Windows 10.

Further Information and Manual Repair

Caution: The following steps are complex and need to be done by experienced users especially using the command line. Once an error is made in entering commands, there’s a chance that your device can be put in a no-boot situation, or data stored on the device can possibly get lost.

To upgrade to Windows 10, your device needs to have at least 15MB free space on the System Reserved Partition. Follow the procedure below and then try upgrading again.

First, know if the System Reserved Partition is whether in GPT or MBR partition style:

1. Open the Run window by pressing the Windows key + R. Type msc in the window then press Enter.
2. Right-click on the Disk where SRP is located then select
3. Click over the Volumes
4. On the Partition Style line, you’ll see which partition style your device is using, either Master Boot Record (MBR) or GUID Partition Table (GPT)

Second, determine which method you will need:

Depending on what partition style your device has and whether you’re currently on Windows 7 or Windows 8/8.1, there are various methods you need to do.

Method 1: Windows 7 or 8/8.1 with GPT partition

1. Click on the Start button and search for cmd. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.
2. Type mountvol y: /s at the command prompt then press Enter. This command will add the Y: drive letter where you can access the System Partition.
3. Type taskkill /im explorer.exe /f then hit Enter. Afterward, restart explorer in Admin mode by typing exe and hitting Enter.

NOTE: While in Admin mode, some apps like OneNote will not run.

4. Open File Explorer then type Y:EFIMicrosoftBoot in the address bar. Hit Enter.
5. Choose the language folders you want to permanently delete. Language folders are named with four letters split with a hyphen. For instance, you want to delete the German language: choose de-DE.
6. Optional: You can also delete unused font files for more space. Type Y:EFIMicrosoftBootFonts in the address bar then press enter.
7. Once you permanently deleted the unnecessary files, reboot the device to return to explorer.exe to normal mode and remove the Y: drive letter.

Method 2: Windows 7 with MBR partition

Doing this method will make a permanent, but small increase in the free space of the device’s SRP.

1. Delete language folders

a. Open the Run window by pressing the Windows key + R. Type diskmgmt.msc then hit Enter. b. Select System Reserve partition then right-click on it.

c. Choose Change Drive Letter and Paths then select Add.

d. Type Y for the drive letter then click OK.

e. Click on the Start button and search for cmd. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.

f. Type Y: at the command prompt then press Enter.

g. Once you’ve switched to drive Y, type takeown /d y /r /f . then hit Enter.

NOTE: Ensure that the space and period after “f” is included in order for the command to work properly      

h. Type icacls Y:* /save %systemdrive%NTFSp.txt /c /t then hit Enter to back up the permission to the drive.

NOTE: Ensure that all files are marked as successful and that no files are marked as failed.

i. Type whoami then hit Enter. Record the username that appears. Afterwards, type icacls . /grant <username you got from whoami>:F /t then press Enter.

NOTE: Ensure that there’s no space between the username and “:F” or the command will not work.

j. In the File Explorer, open the SRP drive and select the Boot folder. Choose the             language folders you want to permanently delete. Language folders are named      with four letters split with a hyphen. For example: de-DE is the German language          while en-US is the U.S. English language.

2. Truncate the NTFS Log:

a. Open the Command Prompt then type chkdsk /L Y: to check the size of the NTFS Log. If the NTFS Log size is less than 5000KB, you need not truncate the file.

b. Type chkdsk /L:5000 /X /F then hit Enter to truncate the NTFS Log.

c. Return to Disk Management window. Select Action menu then select Check if the device’s SRP now has a larger amount of free space. Once there’s enough space, right click the System Reserve Partition then select Change Drive Letter and Paths. Choose Y: then select Remove.

3. If there’s still not enough available space after truncating the NTFS Log, resize the USN journal:

a. Open the command prompt then type fsutil usn queryjournal Y: to display the size in hex value. Convert the hex value to decimal then divide it by 1048576. The result you will get will be in MB. If the journal size is 30MB or more, proceed with truncating the file.

NOTE: To convert the Hex value to Decimal, open the Calculator app in Windows then choose View menu. Select Programmer then choose Hex. Type the Hex value then choose Dec.

b. Type fsutil usn deletejournal /D /N Y: then hit Enter to delete the journal. Type fsutil usn createjournal m=1500 a=1 Y: to recreate the journal having the new log size value.

4. Restore permissions

a. Type icacls Y: /restore %systemdrive%NTFSp.txt /c /t in the Command Prompt. Check if the files were successfully processed before proceeding. If you see a message saying some files failed while processing, this is normal since some of the files have already been deleted before performing a backup. However, if there are no successful files indicated, the command was not properly executed.

b. Type icacls . /grant system:f /t then hit Enter to adjust the ACL back to System. Now, you can set the owner of the drive by typing icacls Y: /setowner “SYSTEM” /t /c then press Enter.

c. Check if the device’s SRP now has enough free space by going back to Disk Management and refreshing the data. If the SRP already has sufficient space, you can now remove the drive letter. Right-click on the System Reserved Partition then choose Change Drive Letter and Paths. Select the Y: drive then choose Confirm deleting the drive letter by clicking OK.

Method 3: Windows 8/8.1 with MBR partition

This method makes a larger, but temporary, increase in the SRP free space.

1. Be sure you have an external drive having at least 250 MB free space and formatted as NFTS.

2. Open Run by pressing the Windows key + R. Type mscthen to choose the Recovery Partition. Right-click on it then choose Change Drive Letter and Paths.

3. Select Add then type Y for the drive letter, click

4. Click on the Start screen then type cmd in the search bar. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.

5. Switch to another drive by typing Y: in the command prompt. Once you’re in the drive Y, type takeown /d y /r /f .

NOTE: Ensure that space and period after “f” are included in order for the command to work properly.

6. Type whoami then hit Enter. Record the username that appears. Afterward, type icacls . /grant <username you got from whoami>:F /t then press Enter.

NOTE: Ensure that there’s no space between the username and “:F” or else the command will not work.

7. Once the command is completed, type attrib -s -r –h Y:RecoveryWindowsREwinre.wim then hit Enter.
8. Open File Explorer and check the drive letter of the external drive you’re using (In this case, let’s assume F: is the drive letter of the external drive so when you see F: for the rest of the steps, this means the drive letter of the external drive you’re using).
9. Type mkdir F:RecoveryWindowsRE in the Command Prompt then hit Enter. Afterward, type xcopy Y:RecoveryWindowsREwinre.wim F:RecoveryWindowsREwinre.wim /h
10. Type C:WindowsSystem32Reagentc /SetREImage /Path F:RecoveryWindowsRE /Target C:Windows to map the new path
11. Verify if the copy was successfully done then type del Y:RecoveryWindowsREwinre.wim /F
12. Return to Disk Management window. Click on the Action menu then hit Check if the device’s SRP now has a larger amount of available space. Once there’s enough space, you can proceed with the upgrade.
13. Upon completion of the upgrade, move back the wim file to the Recovery Partition. At this point, you can re-map now the location by:
    1. Open the Command Prompt then type xcopy F:RecoveryWindowsREwinre.wim Y:RecoveryWindowsREwinre.wim /h and press Enter.
    2. Type C:WindowsSystem32Reagentc /SetREImage /Path Y:RecoveryWindowsRE /Target C:Windows to re-map to the original path.
14. Return to the Disk Management window. Right-click on the Recovery Partition then choose Change Drive Letter and Paths. Select the Y: drive then choose Remove.

Method: Download a Powerful Automated Tool

Not inclined to go through a long and technical process (as highlighted above)? Download and install a powerful automated tool and get the job done in a jiffy.

It is no longer a secret that websites, social media, and other various places on WEB are tracking you and your messages and emails for keywords that they will later use to promote and serve your specific ads linked to those keywords. Altho the process is fully automated it does feel a little forced and uneasy. That is why we are bringing you this article in which we will show you how to stop website tracking in the most popular and used browsers.

SAFARI

Apple’s Safari browser gives you the option to block cross-site tracking. It also has a Privacy Report that displays all the sites and agencies that are gathering information about you. Before blocking these trackers, you may want to review exactly which sites are tracking you online and gathering information about you. Armed with this information, you may decide that cross-site tracking isn’t a huge issue for your particular browsing habits, or you may decide to avoid certain websites entirely. To access Safari’s Privacy Report:

1. Launch the Safari web browser.
2. In the toolbar, select Safari > Privacy Report.
3. Select the Websites tab. This will display information about all the websites that are profiling you.
4. Select the Trackers tab. This displays a list of all the trackers that are gathering information about you. This includes the companies that created these trackers and the number of times Safari detected these trackers during your browsing sessions.

You can also check how intrusive a particular website is by navigating to the website in question and then selecting the shield icon that appears alongside Safari’s address bar. You can then select Trackers on This Web Page, and Safari will display a list of all the trackers that are active on this particular webpage. Once you’ve seen all the websites and agencies who are tracking you, if you want to block these trackers:

1. In the Safari toolbar, select Safari > Preferences …
2. Select the Privacy tab.
3. Select the following checkbox: Prevent Cross-Site Tracking.

Safari will now prevent these trackers from following you across the World Wide Web.

CHROME

As you’re browsing the web, Chrome can send a request for websites not to collect or track your browsing data. It’s important to note that this is a request, so there’s no guarantee that every website will honor the request. Frustratingly, Chrome doesn’t provide information about the websites that are tracking you online. However, we still recommend enabling this feature, as it can help minimize the number of websites that are tracking your online movements:

1. In Chrome’s upper-right corner, select the three-dot menu icon, then Settings.
2. In the menu on the left, select Privacy and security.
3. Click Cookies and other site data.
4. Find the Do not track slider and push it into the On position.

Now Chrome will send a Do Not Track request to every website you visit. Since this is only a request, you may want to take additional steps to protect your online privacy. Ghostery is a Chrome extension that enables you to view and block online trackers. After installing Ghostery, you can view all the trackers that are active on a particular website:

1. Head to the site in question.
2. Click the Extensions icon in the Chrome toolbar.
3. Select Ghostery to see a list of all the trackers this extension has detected.
4. You can block all of these trackers by selecting the Detailed tab and then clicking Restrict site.

Repeat this process for every site you visit.

MOZILLA FIREFOX

Firefox has an Enhanced Tracking Protection feature that can block all the cross-site trackers identified by Disconnect. This feature can also preserve your online privacy by blocking social media trackers, fingerprints, and crypto miners, making this a great all-arounder for the security-conscious Internet user. Enhanced Tracking Protection should be enabled by default. However, you can verify whether it’s active for your particular Firefox installation by navigating to any website. Next, click the little shield icon that appears alongside Firefox’s address bar and you should see a message confirming that Enhanced Tracking Protection is enabled. If Enhanced Tracking Protection isn’t enabled, we recommend activating it:

1. In Firefox’s upper-right corner, select the three-line icon, then Preferences.
2. In the menu on the left, select Privacy & Security.
3. You can now select either Standard or Strict. Note that Strict may affect the functionality of certain websites, so it’s recommended you opt for Standard unless you specifically require a greater level of protection.

Similar to Chrome, Firefox can send a Do Not Track request. While you’re in the Privacy & Security menu, you may want to consider activating Mozilla’s Do Not Track feature.

OPERA

When you first installed Opera, it gave you the option to block trackers. If you didn’t take Opera up on the offer then, you can start blocking trackers now:

1. Along the left side of the Opera browser, click the cog icon. This opens Opera’s settings.
2. In the menu on the left, select Basic.
3. Find the Block Trackers slider and push it into the On position.
4. Blocking trackers can impact the functionality of certain websites. If you start noticing strange behavior on a particular website, you may want to add that site to your Exceptions list. By allowing this site to use trackers, you should be able to resolve any issues you’re experiencing.

To make an exception for one or more websites:

1. Launch Opera’s settings by clicking the little cog icon.
2. Navigate to Basic > Manage Exceptions.
3. Click Add and then type the address of the site where you want to permit trackers.

Repeat for all the sites that you want to add to your exceptions list.