![Windows 11 dark mode2](https://errortools.com/wp-content/uploads/2021/08/Windows-11-dark-mode2.jpg)
In this post, you will be guided on what to do if the Recent Items are no longer visible in the Taskbar icons in Windows 10. This can be quite inconvenient especially if you work simultaneously on many files and documents together and would require you to visit them regularly to incorporate changes. Thus, if you find that the Recent items are not visible in the Windows Taskbar, read on.
In order for the Recent Items to appear on the taskbar icons in Windows 10 again, there are four potential fixes you can check out. You can try to show the recently opened items via Settings or clear the cache of the recent items. You could also make some changes in the Windows Registry or use the Group Policy Editor.
But before you proceed with these potential fixes, it’s best if you create a System Restore Point first just in case something goes wrong after you made changes in the system. The System Restore Point allows you to undo these changes and bring back the previous state of your computer. Thus, you need to create one and then carefully follow the given options below.
The first thing you can do to fix the problem is to show the recently opened items through the Settings app.
Note: These files are automatically recreated when you interact with the system like performing tasks such as opening apps or accessing files.
The next thing you can do to fix the problem is to apply some tweaks in the Registry by following these steps:
Note: This entry is the one that stores the Group Policy setting for “Do not keep the history of recently opened documents. The Group Policy adds this entry to the registry with a value of 1 if you enable the “Do not keep the history of recently opened documents” policy. On the other hand, if you disable the policy by setting it to “Not configured” or deleting it, the Group Policy will delete the entry from the registry, and the system will act as though the value is 0 – for instance, it keeps the history of the recently opened files in your computer.
Note: If you choose to enable this setting, the system and Windows programs will not create shortcuts to documents opened while the setting is in effect. Aside from that, they also stay but won’t display the existing document shortcuts and the system will empty the Recent Items menu on the Start menu and the Windows programs won’t also display shortcuts in the Start Menu. In addition, the Taskbar won’t also show the recently opened or frequently used folders, files, or websites.
“Component 'MSCOMCTL.OCX' or one of its dependencies not correctly registered: a file is missing or invalid”
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.
“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.
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.
NOTE: While in Admin mode, some apps like OneNote will not run.
Doing this method will make a permanent, but small increase in the free space of the device’s SRP.
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 properlyh. 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.
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.
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.
Upon updating to Windows 10, some users might encounter a blinking or flashing desktop after logging in. This will result in a repetitive restarting of explorer or you won’t be able to make the start menu and shortcut keys work. In addition, the network icon might not appear in your taskbar as well. Other Windows 10 error messages include error code 0xc000021a.
Your blinking or flashing desktop after logging in might be the result of problems with the bushell.dll shell extension, which is a part of the Norton Security Suite. Another possible cause for this annoying problem is an issue with your display driver since not all systems will use the same display driver and will depend on what graphics card you use.
In fixing the bothersome blinking or flashing desktop after logging in problem, you can do a manual repair method to address the root problem. You need to be familiar with the Windows command line to successfully go through the process. However, if you are not knowledgeable or confident enough to do this on your own, it would be best to seek help from a professional. Or, you might want to consider using an automated tool to solve the issue.
You need to identify first what’s causing the blinking or flashing of your desktop after login to properly address the issue. The following methods can be done if your issue is caused by bushell.dll shell extension issue:
NOTE: Text input is most probably affected by the explorer restarts so you might need to repeatedly type some letters or to carefully input texts.
NOTE: You might need to download the latest Video Driver on a working computer. Save it in a thumb drive then copy and install it on your computer. If in case there is no native Windows 10 driver, you can also download the latest Windows 7 or Windows 8.1 video driver. Afterward, install it in compatibility mode.
0x80004001 is an error code that Windows users encounter quite commonly.
This error usually occurs when users try to update an old Windows application or attempt to run a certain application. When this error appears on the screen, the system automatically restarts to stop further processing. The error results in a blue screen after the system boots.
This blue screen is known as the Blue Screen of Death.
There are different files in the Windows operating system responsible for its smooth functioning. Sometimes problems like viruses or incorrect register entries corrupt or damage these files. This is when this 0x80004001 error appears.
Simply put, some of the most common causes that trigger 0x80004001 error are listed below as follows.
Irrespective of what causes this error, it is of utmost importance to troubleshoot it as soon as possible.
While there are several ways of troubleshooting this error, the two most useful approaches have been listed below as follows.
Use any of the methods listed above to get rid of the 0x80004001 error once and for all.