If you were trying to open File Explorer but it suddenly stopped working and you encounter an error message that states, “An attempt was made to reference a token that does not exist”, read on as this post will guide you in fixing this problem. This problem was initially reported after the April Update and Microsoft was able to fix it right after correcting the build. However, this effort seems futile for some users as recently, some reported getting the same error when they try to open not just Windows File Explorer but also with utilities like Microsoft Management Console or MMC, Visual Studio, Task Manager, Printer, Recycle Bin, etc.
Two of the most likely causes of this error are a troublesome Windows Update and corrupted system files. Whatever the cause is, here are some suggestions you can follow to fix the “An attempt was made to reference a token that does not exist” error.
You may have to re-register the ntdll.dll file using the regsvr32.exe before you can successfully install the program and fix the ntdll.dll file crash error. The Regsvr32 tool is a command-line utility that can be used to register and unregister OLE controls like DLL and ActiveX (OCX) control in the Windows operating system. Follow the steps below to use it.
Note: Replace “[DLL file]” with the name of the DLL file that was pointed out in the error.
The System File Checker or SFC scan could detect and automatically repair damaged system files that could be causing the “An attempt was made to reference a token that does not exist” error to pop up. 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 with good system files. To run the SFC command, follow the steps given below.
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:
This kind of error might have something to do with a Feature Update so you can try to revert your computer to a previous build of Windows 10 as it could help you fix the problem. In this case, it would better if you refrain from updating your Windows 10 computer until this problem is completely resolved by Microsoft.
“The scratch directory size might be insufficient to perform this operation”This kind of error in DISM occurs when the DISM command is executed from the Windows Recovery Environment due to the limited size permissions of a delivery where the operating is being performed. To fix this DISM error, you need to follow the instructions laid out below. Step 1: First, tap the Win + R keys to open the Run utility and then type “cmd” in the field and tap Enter to open Command Prompt. Step 2: Next, you have to specify a scratch directory that contains the Windows folder and to do that, you can either use the DIR command or the BCEDIT command. So in the elevated command prompt type and enter “dir” or “bcedit”. Step 3: After that, you will see a list of folders inside the C: partition. Now you have to create a folder named “scratch” inside the partition. To do so, execute the following command:
mkdir C:ScratchNote: The command you just entered will create a directory inside the root of the C: partition named Scratch. Step 4: Now that you’ve created the Scratch folder, note that each time you run any of the DISM commands, you have to enter the following code snippet in them:
/ScratchDir:C:ScratchNote: For instance, if you are using the DISM tool to repair the offline Windows image, instead of executing the “Dism /Online /Cleanup-Image /RestoreHealth” command, you now have to execute the “DISM /Image:C: /ScratchDir:C: Scratch /Cleanup-Image /Restorehealth” command. And if you want to remove a selected installed update package, you can use the “DISM /image:C: /ScratchDir:C:Scratch /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e75~amd64~~16299.196.4.9” command. Keep in mind that the mentioned package is only an example. And lastly, you also have to replace the drive letter in the new code snippet when you execute the commands given above.
Set-ExecutionPolicy Unrestricted
Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"}Note: In the command given, do not forget to replace the “PackageFullName” with the actual package name for the Photos app. After executing the command, it will uninstall the Photos app from your computer so you need to install it again from the Windows Store by simply looking for it. Once you found it, just click on install to start the installation process.
“This Office visual refresh is based on feedback from customers who asked for a more natural and consistent experience within and between your applications, specifically on Windows. With this update, we deliver an intuitive, coherent, and familiar user interface, using the Fluent Design principles, across all your applications: Word, Excel, PowerPoint, OneNote, Outlook, Access, Project, Publisher, and Visio. We aligned this visual refresh with the design of Windows 11 to provide seamless experiences on your PC.”It is always refreshing to hear when a company listens to its user base and actually does what is needed instead of trying to invent the wheel.
‘Sending and receiving reported error "0x80004005": The operation failed.’ ‘This message could not be sent. Try sending the message again or contact your network administrator. The client operation failed. Error is [OX80004005- 0X0004B9-OXOO501].’