Android apps inside Windows 11

If you are trying to install a Windows 10 upgrade but was interrupted with an error saying, “0x80070003 – 0x2000D, The installation failed in the SAFE_OS phase with an error during MIGRATE_DATA operation”, then you’ve come to the right place as this post will help you sort this problem out. When you get this kind of error while trying to upgrade your computer, although there could be various reasons for this, the primary one is that when you upgrade from one update to another, something stopped the upgrade process to migrate the user data. To fix this error, you can try to run both the DISM tool and the System File Checker to automatically repair any corrupted system files. You could also try checking the free storage space of your primary drive and if you have any file lock apps like BitLocker, consider disabling them for they could also be the reason why you’re getting the error.

Option 1 – 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 which might be the reason behind the Windows Upgrade error 0x80070003 – 0x2000D. 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.
• Once it’s done, restart your computer and then check if the issue is resolved or not on the next startup.

Option 2 – Run the SFC scan

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the Windows Upgrade error to appear. 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. 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 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.

• Reboot your PC.

Option 3 – Try checking the free storage space on your primary drive

The next option you can try to resolve the error is to see if you have enough free storage space on the primary drive because if you don’t then it’s probably the reason why you’re getting this error. To fix it, you need to free up some storage space by following these steps:

• Open Setting > System > Storage from the WinX Menu.
• From there, you will see a list of all the local and connected storage devices along with the details on the free space.
• Now make sure that the Storage Sense feature is turned On then go find a link that says “Free Up Space” and click it to open.
• After that, a screen which is the built-in program in Windows 10 will appear and will scan your computer for the following junk files so you can free up disk space:
• Windows Upgrade Log Files
• System created Windows Error Reporting Files
• Thumbnails
• Temporary Internet Files
• Previous Windows Installation Files
• Delivery Optimisation Files
• DirectX Shader Cache

Note: Once you’re done freeing up space on your drive, try to run the setup file again.

Option 4 – Try disabling BitLocker and other file lock apps

If you are using BitLocker or other file lock apps, then it could be the reason why you’re getting the error. Usually, file lock apps don’t cause any kind of issue, however, if you have something that works on file level like BitLocker, you can try to disable it. Once you’ve disabled it, try to install the Windows 10 Upgrade again and after you do, enable BitLocker again. This should fix the problem.

Error 501 - What is it?

Error 501 is an error code that sometimes may occur while you are using Internet Explorer on your Windows PC. The error message is displayed as:

'Error 501: Not implemented or not supported.'

Solution

Error Causes

It is difficult to narrow down the ultimate cause of error 501. This is because this error code can be triggered by multiple reasons such as:

• Third-party confliction or due to an incorrect HTTP 1.1 setting
• Improper program installation
• Changes in the “LocalAccountTokenFilterPolicy” registry key
• Corrupted Registry Database

Further Information and Manual Repair

The occurrence of this error regardless of what the cause is may cause a lot of inconvenience to you. And if not fixed on the time it can lead to system failure too. To repair the error 501, identifying the cause for the error really helps. By identifying the cause, you can easily select the most suitable solution to fix it.

Let us walk you through the solutions to fix error 501 timely:

Cause: Third-party conflicts or due to an incorrect HTTP 1.1 setting

Solution: If the above cause is the reason for error 501, this means the Local Policy Rights Settings have been altered. And because of that, Windows is not running your desired program. To solve this error simply log on to Windows as an administrator. Then run local computer policy snap-in. Open it and click on the computer configuration. Here you will see the Windows settings option. Click on it and then open security settings, local policies, and click on properties. Now in the add users section select the user which you want to add to the policy and save by pressing OK. After you’ve made changes, now try using internet explorer again. If this is the cause for the error pop, the error will not occur. If it still occurs then this means there is some other underlying cause for the error. Read on to find out.

Cause: Improper Program Installation

Solution: Error 501 may also occur due to improper program installation. The best way to resolve it is to uninstall recently installed programs.

Cause: Changes in the “LocalAccountTokenFilterPolicy” registry key

Solution: Sometimes during installation registry keys also get damaged or changed. If changes in the LocalAccountTokenFilterPolicy” registry key is the issue, then you need to alter the registry key ‘LocalAccountTokenFilterPolicy settings and its value. This key inside the registry database allows Windows to control the various access options that you have. However, due to wrong settings, it denies access and shows error 501 when you open Internet Explorer. To alter registry key settings can be tricky and complex if you are not a computer programmer. In such as scenario it is advisable to download Restoro. This is a user-friendly and multi-functional repair tool embedded with a powerful register cleaner. In addition to this, it also functions as anti-virus and a system optimizer.

Restoro Solution

Restoro is simple and easy to use. To operate this tool on your PC and to reset registry settings you don’t need any technical expertise or sound knowledge. Its smooth navigation makes it easy for users to scan and repair errors like 501 due to registry misconfiguration in seconds.  With this helper, you don’t have to modify Windows registry settings manually. It will do it automatically. Furthermore, if Error 501 is triggered by a corrupted registry database, you can run it to repair this issue too. It cleans and wipes out all the unnecessary and obsolete files that could be corrupting your registry. This includes junk files, internet history, and invalid registry entries. It clears up your hard disk space and repairs your corrupted registry. If your PC’s registry is damaged due to malicious software like viruses and malware, then it uses advanced antivirus to remove them from your system. It has a value-adding backup feature that enables you to create a backup of your files for data safety and recovery in case of loss during repair. Restoro is compatible with all Windows versions.

Starting with Restoro

Here are 3 simple steps to get started:

1. Click here to download Restoro.
2. Once the installation is complete, run it to scan for errors
3. After scanning the errors, simply click repair to resolve the issues including the error code 501.

Along with fixing error code 501 triggered by registry damage, it also repairs all other PC-related issues. It helps maintain a stable and error-free system for the longest time.

To turn password login in Windows 10 you will need approximately one minute of your time. So let's do it fast and efficient Press ⊞ WINDOWS + X to open the secret menu Click on command prompt (admin) Type in command prompt following:

powercfg /SETDCVALUEINDEX SCHEME_CURRENT SUB_NONE CONSOLELOCK 0

press ENTER

powercfg /SETACVALUEINDEX SCHEME_CURRENT SUB_NONE CONSOLELOCK 0

press ENTER And you are done! Next time when you open your laptop from sleep you will no longer need to type in the password.

Windows has a lot of built-in tools that help you fix tons of system-related issues. One of them is the System File Check which is the tool you can use to conveniently replace potentially corrupted or missing system files with good ones. But what happens when it does not work? Well, you’ve come to the right place as in this post, you will be guided on how you can replace a corrupted single Windows system file manually with a known good copy of the file if the System File Checker scan is not working. When you encounter this issue with the System File Checker, it will be unable to replace the corrupted system files and returns an error message instead. And so to fix and replace corrupted system files in your Windows 10 computer without the help of System File Checker, you can refer to the instructions provided below. Step 1: First, you need to open the log files listed below and identify which particular file has been corrupted:

• %userprofile%Desktopsfcdetails.txt
• Log %WinDir%LogsCBSCBS.log

Step 2: You will see all the details on the given log files. Once you find out the name and the path of the file, you have to take ownership of this corrupted system file. Step 3: To take ownership of the corrupted file, you need to pull up Command Prompt by tapping Win + R keys on your keyboard and then type “cmd” and tap Enter. Step 4: After opening Command Prompt, type and enter the command below to execute it:

takeown /f FileNameAndPath

Note: In the given command, “FileNameAndPath” represents the name and the path of the corrupted file. For instance, the corrupted file is named “wuapi.dll”, then you need to type “takeown /f C:/Windows/System32/wuapi.dll” Step 5: Next, you need to grant administrators full access & control to the corrupted file and you can do that via Command Prompt again. Step 6: In the elevated Command Prompt, type and enter the following command to execute it:

icacls FileNameAndPath /GRANT ADMINISTRATORS:F

Note: We’re going to use the wuapi.dll again as an example. So the command should be like this: icacls “C:/Windows/System32/wuapi.dll /grant administrators: F”. Step 7: Now all that’s left to do is replace the corrupted system file with a good copy from a trusted source. Once you have a copy, open an elevated Command Prompt again and execute the following command:

copy NewFileLocation FileNameAndPath

Note: In the command given above, the “NewFileLocation” is the location where you have saved the copy of the file. For instance, if you’ve saved it on your desktop, this is how it should look: “copy C:/Users/<username>/Desktop/wuapi.dll C:/windows/system32/wuapi.dll”

As you know, the Windows Media Creation Tool is a great utility in Windows that helps lots of users in installing Windows on their PCs. However, just like any other program in Windows, it also experiences a couple of issues every now and then. So in this post, you will be guided on how you can resolve a particular issue in the Media Creation Tool which is the error 0x80042405-0xA001A. You can encounter this error while creating a USB installation media used in installing Windows 10. When getting this kind of error in the Windows Media Creation Tool, you will see the following error message on your screen:

“We’re not sure what happened, but we’re unable to run this tool on your PC, Error code 0x80042405 – 0xA001A”

The error 0x80042405 – 0xA001A occurs while creating a bootable USB installation drive. This is a common error faced by many users and it has something to do with the USB hardware. To get this issue fixed, here are some suggestions you could check out.

Option 1 – Try to reformat the USB drive

Reformatting your USB drive might help in fixing error 0x80042405 – 0xA001A.

• Open This PC and right-click your USB drive from there then select Format.
• Next, select FAT32 as the drive type and uncheck the “Quick Format” option.
• After that, try to run the Windows Media Creation Tool again and check if the error is fixed or not. But hopefully, it should work since formatting the drive as FAT32 will give the driver a proper type and would resolve any minor issues in the drive.

Option 2 – Copy the Windows Media Creation Tool to the USB drive

If the first option didn’t work, you might want to copy the latest version of the Media Creation Tool to the USB drive. After you do that, you can run it from inside the drive. This is actually a working fix and can definitely get the USB drive to run with Windows inside it so it should resolve the error 0x80042405 – 0xA001A on the Windows Media Creation Tool.

Option 3 – Run CHKDSK to check the drive for errors

When it comes to some issues concerning the hard drive or removable devices, there is a utility in Windows that might help which is called “chkdsk”. This error check utility can help with several issues in the system including the “Diskpart failed to clear disk attributes” error.

• Tap the Win + S keys to open the Search box.
• Then type “command prompt” in the field and from the search results that appear, right-click on Command Prompt and select “Run as administrator”.
• After opening an elevated command prompt, copy and paste the following command and hit Enter:

CHKDSK [volume [[path] filename]] [/F] [/V] [/R] [/X] [/C] [: size]]

Note: In the command given above, “[/F]” will try to fix the system errors while “[/R]” will be the one to fix the bad sectors.

• Now if you are prompted to run CHKDSK after your reboot your PC, just tap Y and reboot your PC.
• If CHKDSK is not able to find any errors, tap the Win + E keys and navigate the access window. From there, right-click on the concerned drive and click on Properties.
• After opening Properties, click on the tab Tools and then click on the “Check” button under the Error-checking section.
• Wait until the process is completed and then restart your computer.

Option 4 – Try checking the hardware components

On the other hand, it is also possible that the issue has something to do with a hardware problem and so you need to check the hardware components on your computer to determine that.

Mapping network drive has many benefits in terms of speed and ease of access of files via network. It lets you access the hard drive over the whole network like it was the hard drive inside your PC case. In order to easily and quickly map a folder as a network drive follow the guide below.

1. Open File Explorer
2. Click on the three dots icon in the Toolbar
3. Select Map Network Drive
4. Click the Drive drop-down menu
5. Select a driver letter that you wish to assign as a network drive
6. In the folder field enter network device and share name (click on browse to see all devices on local network)
7. Check the box beside Reconnect at sign-in if you wish to automatically connect to a network drive on Windows startup
8. Check Connect Using Different Credentials if you wish to connect to a network drive using different credentials that one used to login into Windows.
9. Click Finish

After finishing setting Windows 11 will try to connect to the network drive and if successful drive icon will appear inside File Explorer and the drive will open up to see its content. If for any reason it cannot connect try checking user credentials, cables, network adapters, etc.

Recently, several users reported an issue on their Windows 10 computers where the taskbar is not visible when they tried to connect to a computer via Remote Desktop Protocol or RDP. The Remote Desktop Connection feature uses the RDP which allows users to access a computer remotely. This is actually different from the taskbar being hidden automatically until the pointer hovers on it since, in this scenario, the taskbar is completely not accessible which makes using the remote computer entirely difficult, if not impossible. There are several suggestions you can check out to resolve this problem, you can try to restart the process of Windows Explorer via Task Manager or you could clear the cache for multiple processes. You could also try to reinstall the Shell Experience components or show the local taskbar in the Remote desktop. Moreover, you could also try to update, uninstall or roll back the display driver/graphics card driver. For more details, refer to each one of the options given below.

Option 1 – Try to restart the Windows Explorer process

The first option you have to try to fix the problem with the taskbar is to simply restart the Windows Explorer process in the Task Manager.

• Tap the Ctrl + Shift + Esc keys to open the Task Manager.
• Next, go to the Processes tab and find the process of Windows Explorer.
• Once you find it, right-click on it and select Restart to restart its process.
• After that, restart your computer and see if you can now see the Taskbar.

Option 2 – Try clearing the cache of multiple processes

The next thing you can do to resolve the problem is to clear the cache of many processes in your computer. To do so, follow these steps:

• Open the Notepad app and paste the following content in the text area:

@echo off taskkill /f /im explorer.exe taskkill /f /im shellexperiencehost.exe timeout /t 3 /NOBREAK > nul del %localappdata%PackagesMicrosoft.Windows.ShellExperienceHost_cw5n1h2txyewyTempState* /q timeout /t 2 /NOBREAK > nul start explorer @echo on

• After that, tap the Ctrl + S keys to save the changes you’ve made in Notepad and select the “All files” as its file type, and then name it “CacheClearTWC.bat”.
• Next, go to the location where you saved the file using File Explorer and then run it. This will run a couple of batch scripts which will clear the cache of multiple processes in the system.
• Tap the Win + X keys and select the “Windows PowerShell (Admin)” option to open PowerShell as admin.
• Next, execute this command in the command line: Get-appxpackage -all *shellexperience* -packagetype bundle |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + “appxmetadataappxbundlemanifest.xml”)}
• After the command has been executed, this will reinstall the Shell Experience components and should fix the problem with the taskbar.

Option 4 – Update, uninstall or rollback the Graphics card drivers

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in MSC into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. 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.

The Windows 10 operating system comes with a user-friendly interface as well as better security features compared to its previous versions. One of these new features is the “Recently Opened Files” feature which displays all the files you’ve opened recently in File Explorer. Although it might seem useful, some users see this as a privacy concern especially if there are other users that use the same computer. If you are one of these users, read on as this post will guide you on how you can disable the “Recently Opened Files” feature in Windows 10. There are three ways you can disable the “Recently Opened Files” feature. You can manually clear the recent files, or disable the feature via Control Panel. You can also do it using the Group Policy Editor.

Option 1 – Manually clear the recent files

The first thing you can do is to clear the recent files manually. Since the information about the recently opened files is stored in the form of cached data, you can locate this data and delete it manually, from time to time. To do that, follow these steps:

• Tap the Win + R keys to open the Run utility and copy this address in the field: %AppData%MicrosoftWindowsRecent
• Next, tap the Ctrl + A keys to select all the items and then tap the Shift + Delete keys simultaneously.
• After that, a prompt will appear where you have to click on Yes. This will delete all the recently opened files in the File Explorer the next time you open it.

Option 2 – Disable the feature via Control Panel

The next option you can try to disable the feature is via Control Panel. Refer to these steps to do so:

• First, click on the Start Menu button and select the Settings icon.
• After that, click on Personalization and then on Start located on the left pane.
• Next, scroll down until you see the “Show recently opened items” in Jump Lists on the Start or the Taskbar and click on it and then toggle it off.

Option 3 – Disable the feature using the Group Policy Editor

If you are using the Windows 10 Pro version, then you have access to edit the functions in the Group Policy. The Group Policy function has the option that can disable all the default services of Windows 10. Note that in this step, you will permanently disable the “Recently Opened Files” feature. So before you proceed, make sure that you really want to disable this feature permanently and not in the meantime.

• Tap the Win + R keys to open the Run dialog box and type “gpedit.msc” in the field and click OK or tap Enter to open the Group Policy Editor.
• Next, on the left side pane, click on the “User Configuration” option and then click the “Administrative Templates” option.
• After that, select the “Start Menu and Taskbar” option and select the “Don’t keep the history of recently opened documents” option in the right pane.
• Now double click on this option and check the “Enabled” option and then click on Apply and OK buttons to save the changes made.

Microsoft sent an email to users on the Dev build channel saying that the company intends to push some builds that don’t represent what consumers will receive with Windows 11 when it officially releases. In other words, these are going to be some rather buggy builds that won’t be too enjoyable to use. The company recommends users switch from the Dev to the beta channel if they aren’t prepared to deal with the instability. We’ll have to wait and see just how buggy these builds are, but if Microsoft is actually sending out a warning about them it is very likely that builds will be plagued with issues and maybe even stability problems.

Back to Windows 10

How we can expect some buggy build of Windows 11 if you prefer a stable system over new features maybe best decision would be to switch back to Windows 10 until the new OS hits official release.

Switching from dev build channel to beta channel

Another solution, if you do not want to deal with too many issues, is to switch from Dev build channel to beta where things will be more stable. Follow the guide below in order to quickly switch to the beta channel. Following instructions only apply to Windows 11 installations that are linked up to the Windows Insider program, not clean installation of OS.

1. Press ⊞ WINDOWS + I to open settings
2. Inside settings click on Windows update
3. In Windows Update click on Windows Insider Program
4. Inside click on Choose your Insider Settings
5. Click on the button next to Beta Channel to select it (you can switch back to the Dev channel here if you change your mind)

The setting will be saved automatically and from now on you will only receive beta channel updates.

The file is too large for the destination file system is the error when you try to copy a file larger than 4GB on a drive formatted in the FAT32 file system. FAT32 is the old file system used in previous Windows versions and it was replaced by superior NTFS, altho FAT32 is still used because of its compatibility fact that it could be accessed in various operating systems its disadvantage among others is that it can not hold files larger than 4GB in size. This refers to the size of a single file, so if you have a file that is this large and when you try to copy or move it on a drive formatted in FAT32 you will get this message, and the operation will not be able to complete.

Format drive

In order to actually transfer the file in its glorious size, I am afraid that you will need to format destination drive in NTFS or if you have data on drive which you do not want to lose with formatting, use third-party software to convert file system from FAT32 to NTFS without losing data. I would recommend AOMEI partition assistant, it is a free and proven application letting you both manage your partitions and convert any one of them into another file system without data loss. You can get AOMEI here.

Split file

Another option if you are not keen on installing third-party tools or formating is to divide large files into smaller ones that are less than 4GB in size. You can use any archiving application since built-in Windows ZIP support will not let you split file into various different sizes. The best tool in my humble opinion is WinRAR, but you can choose any proven one. When file is split into parts less than 4GB in size, you will have no issues copying or move the file to the destination drive.