Can’t download anything on your Windows PC

As you know, each one of the Windows 10 versions is priced differently and one of the considered more expensive compared to the Windows 10 Home version is the Windows10 Pro. The good thing is, Microsoft allows its users to upgrade from the Windows 10 Home version to the Windows 10 Pro version at a reasonable cost instead of buying the entire license again. However, upgrading your Windows 10 computer is not always that easy and you might encounter some errors along the way. One of the reported errors you could encounter is an error message that says, “Something happened, and we couldn’t start the upgrade”. This kind of problem is due to the problems with the Microsoft Store or the key authorization and to fix it, there are several options you can check out. You can try to run the built-in troubleshooters such as the Windows Update troubleshooter, Windows Store Apps troubleshooter, or Microsoft Accounts troubleshooter. You could also try to reset the Windows Store cache or re-register the Windows Store app. For more details, refer to each one of the given options below.

Option 1 – Try to run the Microsoft Accounts troubleshooter

Since the Microsoft Accounts troubleshooter is not built-in into the Windows operating system, you can download this troubleshooter by clicking on this link.

Option 2 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the “Something happened, and we couldn’t start the upgrade” error. 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.

Option 3 – Run the Windows Store App troubleshooter

The Windows 10 Store Apps Troubleshooter will help you in fixing the problem in Microsoft Store. This is a great built-in tool from Microsoft that helps users fix any app issues. To use the Windows Store Apps Troubleshooter, follow the steps below.

• Tap Win + I keys again to open the Windows Settings panel.
• Go to Update & Security and then go to Troubleshoot.
• Under the Troubleshoot section, on your left-hand side, scroll down to find Window Store Apps.
• Then click on the Run the troubleshooter option and follow the on-screen instructions and then see if it fixes the problem.

Option 4 – Try to reset the Microsoft Store cache

As you know, like any other apps, Microsoft Store also caches as you view apps and games so it is most likely that the cache is no longer valid and must be removed. To do so, follow the steps below.

• Right-click on the start button and click on Command Prompt (administrator).
• Next, type in the command, “wsreset.exe” and tap Enter. Once you do, the command will clear the cache for the Windows Store app.
• Now restart your PC and afterward, try opening Microsoft Store again and then try to install your app or update your computer again.

Option 5 – Try to re-register the Microsoft Store app via Windows PowerShell

• Tap the Win + X key combination or right-click on the Start button and click on the Windows PowerShell (Admin) option.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed and open the Windows PowerShell window.
• Next, type in or copy-paste the following command to re-register the Microsoft Store app and tap Enter:

powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRootWinStoreAppxManifest.xml

• Wait for the process to be completed and then restart your computer.

Option 6 – Try contacting Microsoft

If none of the options worked, you might also want to contact Microsoft for further assistance in fixing the error.

If your Microsoft Edge browser encountered a Stop Error that says, “INVALID_POINTER_READ_c0000005 (atidxx64.dll)” in your Windows 10 computer, then this indicates that your Graphics card driver is outdated. According to security experts, Microsoft has already acknowledged the problem and stated that this issue exists with Windows 10 v1809, Windows Server 2019, and Windows Server version 1809. Although there is no direct way to resolve the problem, there are still some workarounds you can try. If you are using a RadeonHD2000 or HD4000 series video card, the update will be blocked for you. Some users also claim to experience performance issues with the lock screen or the ShellExperienceHost. However, if you are using AMD, the problem is that it no longer supports Radeon HD2000 and HD4000 series graphics processing units or GPUs. Even though Microsoft is already working for a way to resolve the problem, here are some alternative solutions you can check out:

Option 1 – Update your Graphics card drivers

• 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: You also have the option to 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.

Option 2 – Try removing AMD Radeon HD2000 and HD4000 drivers

Although this is not exactly a perfect solution, removing AMD drivers will make the operating system fall back to the default GPU available on your motherboard. You also have the option to completely disable the hardware.

• Tap the Win + X + M keys to open the Device Manager.
• Next, look for your Graphics card drive, and under Display Adapters, right click on them and click Uninstall device or Disable device.
• After that, restart your computer. This will disable the AMD drivers so you won’t be able to find them. It will also release the Windows 10 v1809 update on your computer and in case your operating system tries to prompt you with the “New Device found” message, simply ignore it.

Option 3 – Try to use another browser

You might want to use another browser especially when you already updated your computer and Microsoft Edge still keeps on crashing. You can use Google Chrome, Mozilla Firefox, and other browsers as alternatives until you sort out the problem.

Option 4 – Try to remove the Graphics card physically

You might also want to try removing both AMD Radeon HD2000 and HD4000 as they are very old graphics cards. And since AMD is not going to roll out anything, at least on its own if your motherboard has an onboard GPU, it would be best to get rid of the cards. After that, install the Windows v1809 update and then put them back in. You also have the option to install the driver but just don’t use Microsoft Edge.

What Is STOP 0x00000014 Error?

0x00000014 error is actually an error that is always displayed on a STOP message.

It is also known as Blue Screen of Death, abbreviated as BSOD. When this error occurs, the message that is displayed to the user either says ‘STOP: 0x00000014’ or states ‘CREATE_DELETE_LOCK_NOT_LOCKED’. It is crucial to fix this error to ensure your program is functioning appropriately. If this error message is not rectified, you might be opened to other error messages, such as error code 0x000000d1. 

Solution

Error Causes

As far as the causes of STOP 0x00000014 error are concerned, this error usually occurs when a device driver or hardware problem occurs. This error may also occur if users attempt to run some specific application or update or modify an existing application. When a 0x00000014 error occurs, the operating system restarts to disable the PC from performing any further.

Without taking into consideration the causes of its occurrence, it is crucial to make sure that the 0x00000014 error is fixed as soon as possible to eliminate any undesired inconvenience in the future.

Further Information and Manual Repair

A lot of times when an operating system tries to recover from the STOP 0x00000014 error, the user is prompted that Windows has recovered from an unexpected shutdown.

However, if Windows fails to recover on its own, manual repair has to be performed.

While there are several ways this error can be fixed, some of the most effective and efficient ways of troubleshooting the 0x00000014 error are listed below as follows.

• Restart your computer. Often simply restarting the computer can help eliminate the problem.
• If restarting the system doesn’t help, find if you have recently modified or altered any hardware or driver. It is possible that the 0x00000014 error has been caused by the recent modification. Undo the changes and find out if the error occurs again. If it doesn’t, it is highly likely the issue has been resolved.

However, if the error persists, some solutions that may work are outlined below.

• Start your system using the Last Known Good Configuration. This will undo any changes in the driver and recent registry.
• Another solution is to manually perform System Restore. This will also return the system back to its former state.
• Another idea that my work is to use roll back the device driver. When the driver will return to its previous version, the problem will easily be resolved.

To keep the 0x00000014 error from occurring in the future, it is advised to unplug any newly installed hardware or reinstall any deleted software.

If you're not tech-savvy and wish to get this error code rectified in a jiffy, download a powerful automated tool and perform a computer scan.

Recently, a number of users reported an error while trying to update their computers. This particular Windows Update error has an error code of 0x80073701. If you are one of the users who encounter this error, then read on as this post will guide you on how exactly you can fix it. Here’s the exact context of the error:

“Updates failed. There were problems installing some updates, but we’ll try again later. 2019-07 Cumulative Update for Windows 10 Version 1903 for x86-based Systems (KB4507453) – Error 0x80073701”

The Windows Update Error 0x80073701 also comes with a code “ERROR_SXS_ASSEMBLY_MISSING” which indicates that some system files are missing on your computer that caused the update installation failure error. Although this Windows Update error does not cause any severe issues, it is still being reported in the section of Windows Update where it is marked as “Update failed”. There are several potential solutions you can check out to resolve this error. You can try to run the DISM tool or the SFC or System File Checker scan. You could also try to run the Windows Update troubleshooter. For more information, make sure to follow the options given below.

Option 1 – Restart your computer and try installing the Updates again

Restarting your computer can also help in fixing the Windows Update failed to install error 0x80073701. There are cases where the issue resolves on its own as it could just be some simple network or PC error.

Option 2 – Try to run the DISM tool

Running the DISM Tool helps in repairing the Windows System Image as well as the Windows Component Store in Windows 10. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt as admin.
• Then type in this command: 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.

After you run this tool, a log file is created at C:WindowsLogsCBSCBS.log. On the other hand, if the Windows Update client is already broken, you will be prompted to use a running Windows installation as the repair source or use a Windows side-by-side folder from a network share, as the source of the files. Although the chances of this happening is less, if it turns out to be the case, you need to run an advanced command in the DISM tool to repair a broken Windows Update. Just repeat the process above but use the following command instead:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindows /LimitAccess

Option 3 – Try to run the 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 causing the error 0x80073701. To run the SFC command, follow the steps given 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.

Option 4 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update error 0x80073701. 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.

The Windows 10 Telemetry and Data Collection features are auto-enabled and they collect all sorts of user activity and sends it to Microsoft. Microsoft says that the data collected only enhances the overall user experience and Windows functionality better but the number of data breaches happening across the globe has forced users to be extra cautious about their data privacy. So naturally, from stronger passwords and other services management, it is only logical to turn off Windows data gathering. To do so:

• Press ⊞ WINDOWS + R to open the run dialog.
• In the Run dialog type: taskschd.msc
• Press CTRL + SHIFT + ENTER key combo to open Task Scheduler in admin mode.
• On the left pane, navigate to the: Task Scheduler Library > Microsoft > Windows > Customer Experience Improvement Program
• At the location, on the middle pane, right-click on the task named Consolidator and select Disable from the context menu...
• Repeat the process with all other tasks listed in the middle pane.
• Exit Task Scheduler.

Windows users need to be on high alert. Microsoft has confirmed a critical vulnerability has been found in all versions of Windows which presents an immediate threat, and you need to act now. A critical new zero-day hack has been found which affects all Windows versions. Tracked as CVE-2021-34484, the “zero-day” flaw enables hackers to breach all versions of Windows (including Windows 10, Windows 11, and Windows Server 2022) and take control of your computer. Microsoft mistakenly thought it had patched the vulnerability (which was first found in August) when it was publicly disclosed in October. But the fix itself was found to be flawed, something the company admitted, and this drew even more attention to the vulnerability. Microsoft subsequently promised to “take appropriate action to keep customers protected” but two weeks later, a new fix has still not arrived. Luckily the third-party security specialist 0patch has beaten Microsoft to the punch with a ‘micropatch that it has now made available for all Windows users “Micropatches for this vulnerability will be free until Microsoft has issued an official fix," 0patch confirmed. You will need to register for a 0patch account and install its download agent before the fix can be applied, but with 0patch fast becoming a go-to destination for hot fixes which beat software companies to the punch this is a no brainer. Hopes will be high that Microsoft can release an effective patch sooner rather than later but, until then, all Windows users must act now if they want to be safe. Download 0patch here: https://blog.0patch.com/2021/11/micropatching-incompletely-patched.html

As more and more people get into insider preview of upcoming Windows 11 we will see more and more different takes and opinions on it. Generally speaking, the first wave was quite positive when it was previewed but how time is passing more and more limitations and frustration comes to the surface. Some of the limitation that is inside it, which have been confirmed by Microsoft itself includes features missing that we had in Windows 10 like moving the application to the taskbar in order to pin it, moving the file in the taskbar to open it in default application and some big annoyances like Windows opening widgets always in Edge no matter what is your default browser. Not being able to move the taskbar from the bottom is also one of many illogical things. There is not really a point in these missing features since they were working fine in Windows 10 and many users liked them since they could customize Windows more to their liking, now with this new look at limitations it reminds me personally much of apple macOS and I will be honest, I am not a big fan of that kind of thinking. If I wanted that kind of OS I would have gotten myself a MAC, not custom build PC, but hey, Linux is always a free alternative, and how Microsoft itself is pushing limitations and in my opinion bad design choices along with awful system requirements that might just be a case for a lot of users. I am really not sure what is logic behind these moves and I am sure they have their reasons but this time it seems that their take on the new OS is not resonating well with the overall user population, well at least what I have heard so far. Things of course can still be changed and made for the better and I would rather see release postponed and issues addressed than getting more system hogging and limited new OS that at its current state looks like reskinned Windows 10 with limitations.

The previous Windows versions all came with Microsoft's browser Internet Explorer. A lot of users love it because not only that it is easy to use. It is also very fast. Users didn’t have to worry about compatibility because it is almost always compatible with its Windows Version. When they introduced Windows 10, they changed the name of the browser from Internet Explorer to Microsoft Edge. It is faster and more user-friendly compared to its predecessors. But after the Creator Update, some experienced receiving the inet_e_resource_not_found error code. In contrary to what everyone expects, you actually don’t have to uninstall and reinstall the Microsoft Edge App. What you can do is reset the browser in your Apps & Features Settings in your Microsoft Settings.

To reset the browser you can follow the steps below:

1. Click on the Windows icon and go to settings.
2. Click on Apps and this will bring you to the Apps & Features page. Look for Microsoft Edge from the list of Apps and click on it.
3. Choose Advance Option
4. Scroll down then Under Reset, click on repair or reset. When you repair it will fix the existing problem but the data that caused the problem may still be present and can still cause problems. If you click on reset, it will delete all the cache and cookies that are installed in your browser but it will save your Favorites as well as your bookmarks.

Another way to resolve this is by disabling the feature TCP Fast Open on Microsoft Edge. To disable this, go ahead and follow the steps below:

1. Open the Microsoft Edge browser.
2. Type in about: flags on the Address (URL) bar.
3. Under Networking, uncheck the Enable TCP Fast Open.
4. Close your Microsoft Edge browser and open a new one.

Flushing the DNS also worked for other Users. Sometimes, the error code the inet_e_resource_not_found is caused by a corrupted DNS cache. There are 2 ways to flush your DNS. The first option is to use the command prompt to run the command.

1. To access the Command prompt or CMD, you can search for it on Cortana or you can click on the Windows icon to access the Programs, scroll down to the Windows System folder and click on it.
2. A dropdown menu will show up, click on Command Prompt which is the first on the list.
3. Type in the code ipconfig /flushdns and press enter.
4. There will be a message that will show that says Windows IP configuration successfully flushed the DNS Resolver Cache
5. Exit the CMD by typing exit and press enter.

The easiest way to do this is to Press the keys Window + R on your keyboard. Type in ipconfig /flushdns in the search box and hit enter or click on OK. These are only some of the ways to resolve the inet_e_resource_not_found. There are other ways to further troubleshoot this issue such as reinstalling your Wifi Adapter Driver or adjusting the DNS Server Address. But most of the time, users are able to resolve the issue with the steps provided above.

Socket Error 10013 - What is it?

Socket error 10013 is an error code that often pops on the screen when you try to access the server. This error code restricts your permission to access. It shows that your permission request was denied. The error message is displayed in the following format:

“Socket.error: [Errno 10013] an attempt was made to access a socket in a way forbidden by its access permissions”

Solution

Error Causes

Narrowing down a particular reason for the cause of socket error 10013 is difficult, typically because this error code can be generated due to several reasons. Here are some of the common reasons for its occurrence on your PC:

• High-security set up- Firewall or an antivirus program
• Too many functions tied to the same driver confuses the socket
• Outdated drivers
• Malware

The good news is that the socket error 10013 is not fatal. However, it is advisable to fix and resolve the issue to avoid inconvenience.

Further Information and Manual Repair

Here are some of the best, quickest and easiest methods to work around the problem and resolve socket error 10013 without any hassle or delay.

Method 1 - Turn off Firewall

Believe it or not, a high level of internet security measures like Firewalls and anti-virus programs are a common cause of socket error 10013. Firewalls are made to protect a computer from harmful connections but sometimes it may also restrict server connections, considering them as a threat to your system security. Due to this, permission access is adamantly denied. To resolve this issue on your PC, the best way to go about is to turn off your Firewall or any other anti-virus programs installed on your system. Once you turn off these programs, try accessing the server again. The majority of the time the issue is resolved by carrying this step. Nonetheless, if the error still persists, try the methods given below.

Method 2 - Check the Permissions section of the Firewall Program

Another way to resolve this is to check the permission section of the Firewall program and check for the server. If the server is not listed, contact the Internet Service Provider (ISP) and ask for help in adding the server to the list.

Method 3 - Update Drivers

The outdated driver may sometimes be the reason for the socket error 10013.  The socket may no longer use the drivers installed on your PC which is why permission to access the server is not granted. When this is the reason, try updating the drivers to resolve. For new drivers, visit the software manufacturers’ website, download, and install.

Method 4 - Scan for Viruses and Malware

Another alternative is to scan for viruses and malware. Sometimes the cause for the error is a viral infection. Therefore, remove them to resolve. The best way is to download Restoro. This is a user-friendly and next-generation PC Fixer embedded with 6 scanners including a powerful anti-virus. It scans your entire PC and removes all types of viruses including malware, adware, spyware, and Trojans in seconds. Click here to download Restoro.

Steam Deck release is almost upon us and more news comes to light. The Latest officially confirmed technical detail is that the user will have access to device's BIOS and that dual booting will be officially supported. This, of course, means that you will be able to have both Proton and Windows on your device letting you play anything that you wish if the hardware is strong enough. Valve also said that you can launch OS from an SD card! This of course will save space available for games themselves, especially for entry models with less than one available. All of this information really pushes Deck into the territory of a handheld PC and not just another console and I must admit that this announcement left a smile on my face.