USB Keeps Connecting and Disconnecting

Connecting Cortana on Windows and Android

Microsoft's anniversary update has come with many new features and improvements. One of these features is that Microsoft's Cortana can now be installed on your Android phone and as long as you are logged in to your Microsoft account on different devices, she can pass information between devices. You can not see battery life on your desktop PC, notifications, etc. There are some prerequisites in order to get this going, first is to have a Windows version 1607 or newer. The second is to have the last Android version

Installing Cortana on Android

Download and install the Cortana app from the Google Play store.
Open the app and accept the license terms.
Enter the credentials for the Microsoft account you use to sign in to your PC.
After a few seconds, Cortana will open.
Click the settings button and select Sync Notifications.
By default, missed calls, incoming messages, and low battery notifications will be turned on. You can turn this on\off from here. The only option off by default is for App notifications. Any non-system apps such as Facebook and Instagram can also send alerts to your Windows box. You can choose to enable the App notification sync option or leave it off.
If you enable “App notification sync,” you will need to give Cortana permissions to read and control notifications on your phone.
You can then select exactly which applications will be synched to your PC.
Once done you can exit out of Cortana.

Configuring Cortana on PC

Click the Windows button and type Cortana. Click the icon for Cortana and Search Settings.
Scroll through the settings list and look for Send notifications between devices
Click the switch to turn it on.
Sign in to the same Microsoft account you used in the previous section
Navigate back to the Cortana & Search settings tool.
Click Edit Sync Settings. Make sure that your phone shows up on the list. You can also determine if you want PC notifications are sent to your phone.

With those settings in place, you should now start getting alerts for the items you enabled in your Action Center. As notices come in, you will see them pop up in a small bubble on the lower right of your screen. You can dismiss the notification or use the link to find a compatible app in the Windows store.

How to Fix Error 0x8024a206 in Windows

When you upgrade or update your Windows 10 computer but you suddenly got Error 0x8024a206 while trying to install the updates, it is due to a rouge update that was downloaded or because of some corrupted component in Windows. In case you don’t know, any file downloaded by Windows is verified for its integrity and if the files don’t pass the integrity test, then Error 0x8024a206 will most likely pop up during the Windows update or upgrade.

Option 1 – Reset the Windows Update components to the default

You have to stop a couple of services such as BITS, Cryptographic, MSI Installer, and Windows Update Services. And to do that, you need to flush the 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. Aside from that, it also contains all the Windows Update History files and once you delete them, you will most likely lose the Update history. As a result, the next time you run the Windows Update, it may result in a longer detection time.

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 start cryptSvc net start bits net start msiserver

After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
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.

After resetting the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:

Type each one of the following commands.

net start wuauserv net start cryptSvc net start bits net start msiserver

After that, exit Command Prompt and restart your computer, and then try to run Windows Update once more.

Option 2 – Re-register DLLs related to Windows Update

DLL files, also known as Dynamic Link Library, are parts of applications that are separated from the core program so that they can be used again as well as independently be updated. The DLL files are loaded into memory and then used. Note that they have to be registered with Windows so they can be loaded. So if they’re not, the main program will fail. And this is the same with the DLL files related to the Windows Update. Thus, you need to register them in order to resolve Error 0x8024a206.

In the Cortana search box, type “command prompt”.
From the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
After that execute the commands listed below one after the other and don’t forget to hit Enter right after you key in each one of them.
- regsvr32 JSCRIPT.DLL
- regsvr32 MSXML3.DLL
- regsvr32 WUPS2.DLL
- regsvr32 WUPS.DLL
- regsvr32 WUAUENG.DLL
- regsvr32 WUAPI.DLL
- regsvr32 WUCLTUX.DLL
- regsvr32 WUWEBV.DLL

Note: You also have the option to run the commands together via a batch file. Simply create a batch file by copying all the commands in a notepad and then save it as “WURegisterDLL.bat”. After that, run the batch file and it will execute the commands all at the same time. Then you have to restart your computer and see if it has fixed the Error 0x8024a206.

Option 3 – Run the System File Checker

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the Error 0x8024a206. 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:

Windows Resource Protection did not find any integrity violations.
Windows Resource Protection found corrupt files and successfully repaired them.
Windows Resource Protection found corrupt files but was unable to fix some of them.

Option 4 – Run the Windows Update Troubleshooter

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

Fix Chrome is Waiting for cache in Windows

There are times when you may encounter some glitches on your Google Chrome browser in your Windows 10 computer. One of these glitches is when the connection status of Chrome keeps on saying “Waiting for cache” which is displayed at the bottom-left side of the browser in the Status bar. At the time of writing, it isn’t clear yet what could be causing this problem. Although it is possible that it’s caused by browser cache, some extensions in the browser. On the other hand, it could also be caused by the browser profile or due to some fragmented files or that the SSD is occupied. Whatever the cause is, you can check out each one of the given options below to fix the problem.

Option 1 – Try clearing browser cache

There are times when some data in the browser is conflicting with the loading of the website and triggers some problems like “Waiting for cache”. And so you can try to clear your browser’s data. This might be a very basic solution but oftentimes it works in fixing this kind of error in Google Chrome. Follow the steps below to clear the data in your browser.

Open your Google Chrome browser.
After that, tap the Ctrl + H keys. Doing so will open a new panel that allows you to delete the browsing history and other data in your browser.
Now select every checkbox that you see and click on the Clear browsing data button.
Then restart your Chrome browser and check if you can now open any website or not.

Option 2 – Try to disable writing of Cache files to the SSD

You can also disable the writing of Cache files to the SSD to stop Google Chrome’s dependency on the SSD to gather all the cache files.

Option 3 – Delete the User Profile in Chrome

You can also try deleting the User Profile folder in Chrome. To do so, follow these steps:

You need to first end every single process of Google Chrome. To do so, right-click on the Taskbar then select the Task Manager. And if the Task Manager is not responding, you can just use the Alt + Ctrl + Del keys and then select the Task Manager.
After opening the Task Manager, under Processes, look for Google Chrome’s process which would most likely be named “chrome.exe”.
Right-click on Google Chrome’s process and then select the End task option.
Next, tap the Win + R keys to open the Run dialogue box.
Then copy and paste “%USERPROFILE%AppDataLocalGoogleChromeUser Data” and hit Enter.
From there, look for a folder named “Default folder” and then copy the folder to another drive as a backup.
After creating a copy of the folder, delete the Default folder.
Next, open Google Chrome again and go to Settings > Advanced > Reset.

Option 4 – Reset Chrome

Resetting Chrome can also help you fix the error. This means that you will be restoring its default settings, disabling all the extensions, add-ons, and themes. Aside from that, the content settings will be reset as well and the cookies, cache, and site data will also be deleted. To reset Chrome, here’s what you have to do:

Open Google Chrome, then tap the Alt + F keys.
After that, click on Settings.
Next, scroll down until you see the Advanced option, once you see it, click on it.
After clicking the Advanced option, go to the “Restore and clean up option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
Now restart Google Chrome.

Option 5 – Try to clean reinstall Chrome

There are instances when programs leave files behind after you’ve uninstalled them and the same thing can happen to Chrome so before you reinstall Chrome, you have to make sure that you have deleted the User Data folder. To do so, refer to the following steps:

Hit the Win + R keys to open the Run dialog box.
Next, type “%LOCALAPPDATA%GoogleChromeUser Data” in the field and hit Enter to open the User Data folder.
From there, rename the default folder and name it something else, e.g. “Default.old”.
After that, install Google Chrome again and check if the issue is now fixed.

Mapped network drives are not working

When you have to connect to a drive that’s on a different computer or on external storage, that’s where the mapped network drives come in. Mapped network drives make accessing files a lot easier. However, there are times when it won’t work for some reason. Windows will notify you about the unavailability of mapped network drives in several ways. For one, Windows might display a red X on the network drives or it could be that its status will be unavailable when you try to use it from the Command Prompt or via a notification. It is recommended that you run a few scripts when you log in to your PC as it may so happen that the network drive takes more than usual to connect. Before you start troubleshooting the problem using the given options below, keep in mind that some workouts might only work under certain scenarios. You might need some network access at logon or you might need access to the Group Policy settings. So you need to choose what you prefer more. You can try the given workarounds below if the mapped network drives are not showing or connecting or working on your Windows 10 computer. These workarounds use scripts to make sure that you are connected to them as soon as you start to use your PC. As mentioned, before you can troubleshoot, you need to create scripts first. There are two scripts here namely MapDrives.ps1 which is executed by the second script named MapDrives.cmd and is done at a regular and non-elevated Command Prompt. Follow the steps below to get started.

You have to create a script file named “MapDrives.cmd” first and then save it on a place where the files are safe. To do that, open a text editor like Notepad and then copy and paste the following script:

PowerShell -Command "Set-ExecutionPolicy -Scope CurrentUser Unrestricted" >> "%TEMP%StartupLog.txt" 2>&1 PowerShell -File "%SystemDrive%ScriptsMapDrives.ps1" >> "%TEMP%StartupLog.txt" 2>&1

After that, save the file and name it “MapDrives.cmd”.
Next, create a script file named “MapDrives.ps1” and then copy and paste the following content. Just make sure to save both scripts in the same folder.

$i=3 while($True){ $error.clear() $MappedDrives = Get-SmbMapping |where -property Status -Value Unavailable -EQ | select LocalPath,RemotePath foreach( $MappedDrive in $MappedDrives) { try { New-SmbMapping -LocalPath $MappedDrive.LocalPath -RemotePath $MappedDrive.RemotePath -Persistent $True } catch { Write-Host "There was an error mapping $MappedDrive.RemotePath to $MappedDrive.LocalPath" } } $i = $i - 1 if($error.Count -eq 0 -Or $i -eq 0) {break} Start-Sleep -Seconds 30 } Note: Now that you’ve created the script files, it’s time for you to proceed to the options given below.

Option 1 – Try creating a startup item

Note that this option only works on devices that have network access at login. So if it’s not there, the script will fail to reconnect the network drivers automatically. To create a startup item, here’s what you have to do:

Open the Startup folder located at %ProgramData%MicrosoftWindowsStart MenuProgramsStartUp.
From there, copy and paste the MapDrives.cmd.
After that, open the Scripts folder located at %SystemDrive%Scripts copy-paste MapDrives.ps1 and then copy and paste MapDrives.ps1 in there.

Note: After you complete the steps above, a log file named “StartupLog.txt” will be created in the %TEMP% folder. Now all that’s left for you to do is to log out of your computer and then log back in. This will ensure that the mapped drives are open.

Option 2 – Create a scheduled task

It is possible to create a scheduled task that runs as soon as you log in to your computer. To create a scheduled task, follow the steps below.

You have to copy the MapDrives.ps1 script file to the scripts folder of Windows located at %SystemDrive%Scripts.
After that, open the Task Scheduler and select Action > Create Task.
Next, type a name and description of the task in the General tab.
Then click on the Change User or Group button and select a local user group and click OK.
Now check the box labeled “Run with highest privileges” and switch to the Triggers tab.
From there, create a new trigger with the “At Logon” option in the Begin the task drop-down menu and then click OK.
After that, switch to the Actions tab and create a new action then choose to Start a program.
Next, type “Powershell.exe” in the Program/Script field, and in the Add arguments (optional) field, type the following:

-windowsstyle hidden -command .MapDrives.ps1 >> %TEMP%StartupLog.txt 2>&1

And in the Start in the (optional) field, type “%SystemDrive%Scripts” as the location of the script file.
Now under the Conditions tab, select the “Start only if the following network connection is available” option and then select Any connection and click OK.
Restart your computer or log off from your account and then log back in so that the task will be executed.

Option 3 – Use the Group Policy settings

You need this option if the mapped network drives are defined via Group Policy settings. You have to update the action of the drive maps to Replace. As a result, it will delete the existing mapped drive and create the mapping on each logon again. However, any settings on the mapped drive that are changed from the Group Policy settings will be gone on each logon. So if the changes don’t work, you need to run the gpupdate command together with the /force parameter in order to refresh the Group Policy setting quickly.

Error occurred while checking for updates in VLC

There is no doubt that the VLC media player is one of the best kinds of media players available today. However, it is not without any issues and one of the common issues encountered by users is VLC’s inability to be updated. And when you try to update VLC, you only get an error message saying, “An error occurred while checking for updates”. This inability to update VLC can be quite a headache for many users especially the ones who are facing other issues in VLC and has to update it in order to resolve them. So how will you update VLC and fix its issues when you can’t even update it in the first place? Worry not as this post will help you out. Refer to the suggestions laid out below to resolve the issue in updating VLC.

Option 1 – Check if VLC is not being blocked by the Firewall

There are instances when the Firewall like the Windows Defender Firewall blocks VLC for some unknown reason without your knowledge. Thus, you need to allow VLC to get past the Firewall in order for you to fix the issue else you won’t be able to send out a network communication. To do that, follow the steps below.

Tap the Windows key + I to open the Settings app.
Then click on the Update & Security option.
After that, click on Windows Security and click the Open Windows Defender Security Center option. This will open the Windows Defender antivirus and antimalware program.
From there, click on Firewall & network protection.
Next, click on Allow an app through Firewall. You should see a list of programs. Scroll down until you see VLC and make sure that all the boxes are ticked including the Public and Private ones.
Once you’re done, restart your PC and then try updating VLC again.
Just open VLC and select the Help menu and click on Check for Updates.

Option 2 – Try running the VLC media player as an administrator

There are programs designed for Windows 10 that won’t work fully unless some parameters are met. In most cases, starting the program as an admin should resolve the problem, thus, that’s what you have to do to try and fix the “An error occurred while checking for updates” in VLC.

First, right-click on the VLC Media Player desktop icon and then select the “Run as administrator” option or you could also right-click on the icon and click on Properties.
After that, click the Compatibility tab and then tick the box labeled “Run this program as an administrator”.
Next, click the OK button and then open VLC again and try updating it. That should fix the problem.

Microsoft acquires Activision Blizzard

In the latest news, Microsoft has reached a deal to purchase Activision Blizzard for 67.8 billion. Now franchises like Warcraft, Starcraft, Overwatch, Call of duty, Diablo are now the property of Microsoft and I am sure that some of these games we can expect to be included in the Xbox game pass. microsoft activision blizzard

This is the second large game company acquisition by Microsoft, Acquiring Bethesda first and a big hit to Sony since Xbox will now have more games in its catalog and as exclusives. Of course, the sale has to go through the standard closing conditions and completion of regulatory review and Activision Blizzard’s shareholder approval before it’s finalized. Assuming that all goes well, the deal is slated to be completed during the fiscal year 2023, which is July 1, 2022, through June 30, 2023.

Razer is making only 1337 smartwatches

Razer had some strange dives into stuff not really aimed at gamers and the gaming community overall like its Zephir smart mask and now it is venturing into the area of smartwatches teaming up with Fossil. I am not clear if this initiative was set in motion by Razer or Fossil and I really do not know why limited production numbers. Officially named RAZER X FOSSIL GEN 6 SMARTWATCH, this watch comes with the official following text on Razer's page:

Way more. Way faster. Way ahead of the game. Get time on your side with the limited-edition Razer X Fossil Gen 6 Smartwatch—only 1,337 pieces worldwide. Designed for the next generation of gamers, supercharge your style with customizable straps, dials, Razer Chroma™ RGB effects, and more.

Now, I am a fan of Razer and I like their products, mostly keyboards and mouse altho chair is also very good and in top of the product line in that field but I can not really stand behind this product and decision, and the only reason why I can not stand behind it is this 1337 (leet, or elite) a limited number of available pieces that is nothing more than a gimmick to sell watches at a higher price. Watch itself is not really bad, as a matter of fact, it has some solid hardware statistics.

Technical characteristics

Featuring a 1.28-inch AMOLED Display with 3 unique Razer watch faces (Analog, Text, Chroma*), 4 customizable Razer Chroma™ RGB effects, and 2 custom-designed, interchangeable straps, this Razer's baby is packing 44mm, Stainless Steel case with 22mm, straps. It runs on Wear OS by Google as an operating system of a choice and under software, it is packing Qualcomm Snapdragon Wear 4100+ CPU paired with 1GB of RAM and 8GB Storage. The display is running at 416x416 resolution with 326ppi. Watch input is with 2 configurable Push buttons, One rotating Home button, touchscreen, and voice. It has in it a loudspeaker, microphone, and vibration. Connection is via Bluetooth 5.0, GPS, NFC SE, and Wi-Fi. The battery can in their word work for 24 Hr + multi-day Extended Mode **Varies based on usage and after updates install**. USB data cable with magnetic dock snaps to split rings on the watch case back and spins 360 degrees for ease of use. Approximately half an hour to reach 80%. Sensors included in the watch itself are: Accelerometer, Altimeter, Ambient Light, Compass, Gyroscope, Off-body IR, PPG Heart Rate, SPO2. Smartwatch is water-resistant up to 3 ATM & it comes with preloaded apps like: Agenda, Alarm, Battery-Optimized Activity Mode, Calendar, Cardio Level Tracking, Cardiogram, Contacts, Enhanced Phone Dialer App, Google Assistant, Google Fit (Workout, Heart Rate, Goals, Breathe), Google Maps, Google Pay™, Google Play Store, Nike Run Club, Noonlight, Smart Battery Modes, Spotify, Stopwatch, Timer, Translate, Wellness Apps with Sleep Tracking.

Conclusion

Watch is Dropping on 01.10.22, 8 AM PST which is 4 days from now and altho it is an interesting device with solid hardware I can not stand behind it due to its limited edition numbers and with $329 price tag. With the same amount of money, you can get yourself Samsung or Apple watch with more features packing. But of course, that is just my personal preference and if you want to own this limited edition Razer smartwatch, go for it.

How to Resolve “We couldn’t update system reserved partition” Error in Windows 10 Installation

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:

Open the Run window by pressing the Windows key + R. Type msc in the window then press Enter.
Right-click on the Disk where SRP is located then select
Click over the Volumes
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

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.
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.
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.

Open File Explorer then type Y:EFIMicrosoftBoot in the address bar. Hit Enter.
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.
Optional: You can also delete unused font files for more space. Type Y:EFIMicrosoftBootFonts in the address bar then press enter.
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.

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.

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.

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.

Once the command is completed, type attrib -s -r –h Y:RecoveryWindowsREwinre.wim then hit Enter.
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).
Type mkdir F:RecoveryWindowsRE in the Command Prompt then hit Enter. Afterward, type xcopy Y:RecoveryWindowsREwinre.wim F:RecoveryWindowsREwinre.wim /h
Type C:WindowsSystem32Reagentc /SetREImage /Path F:RecoveryWindowsRE /Target C:Windows to map the new path
Verify if the copy was successfully done then type del Y:RecoveryWindowsREwinre.wim /F
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.
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.
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.

Fix GeForce Experience error code 0x0001

The GeForce Experience on graphics card manufactured by NVIDIA is an advantage for users who loves gaming as it makes enhances users’ gaming experience. However, there are times when it may also encounter some problems. One of the problems users may encounter is the error code 0x0001. This kind of error occurs when users open the NVIDIA GeForce Experience utility. Here’s the full content of the error message:

“Something went wrong, try rebooting your PC and then launch GeForce Experience, ERROR CODE: 0x0001.”

Errors like this one diminish the overall experience of users due to the fact that when this error occurs, the NVIDIA GeForce experience wouldn’t even start which renders its features useless. There are several potential fixes you can check out to resolve this error but before you check them out, you can try to restart your computer first and then open the NVIDIA GeForce Experience once again, if you still encounter the error, then you need to check the NVIDIA Display Driver Services or update your NVIDIA display drivers or switch to the BETA release. You could also try to install and reinstall the NVIDIA display drivers or perform System Restore and see if it helps. For detailed instructions, follow the given options below.

Option 1 – Try to check the NVIDIA Display driver services

Tap the Win + R keys to open Run and then type “services.msc” in the field and hit Enter to open the Services Manager.
From there, look for the following NVIDIA services and make sure that their Startup types are as follows:
- NVIDIA Display Container LS – Automatic
- NVIDIA NetworkService Container – Manual
- NVIDIA LocalSystem Container – Automatic
- NVIDIA LocalSystem Container – Automatic
- NVIDIA GeForce Experience Service – Automatic (Delayed Start)
- NVIDIA Geforce Experience Backend Service – Automatic (Delayed Start)
- NVIDIA Telemetry Container service – Automatic
Next, double click on each one of the services and go to Properties. Here, check if the service is running. If it’s not, just click on the Start button. On the other hand, if they’re already running, just click on Stop and then click on Start again.

Option 2 – Try to update the NVIDIA Display drivers

You can also try updating the NVIDIA display drivers as it might help in fixing the error. To update them, follow the steps below.

Tap the Win + R keys to open the Run dialog box.
Next type in “dxdiag” in the field and click OK or hit Enter to open the DirectX Diagnostic Tool.
From there, you can see what type of NVIDIA graphics card that your system is on.
Take note of your graphics card information and then look for the best drivers for your operating system. Once you’ve downloaded and installed the file, restart your PC.

Note: If you want to try out the beta release of the NVIDIA display drivers, click on this link. Beware though that the beta software is unstable and buggy and may cause some different bugs.

Option 3 – Try to roll back the driver to the previous version

If updating the NVIDIA display drivers didn’t work for you, then it’s time to roll back the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh.

Tap the Win + R keys to launch the Run window and then type in the “msc” command and hit Enter to open the Device Manager window.
Under the Device Manager, you will see a list of drivers. From there, look for the NVIDIA Drivers and expand it.
Next, select the driver entries that are labeled appropriately.
Then select each one of them and double click to open a new mini window.
After that, make sure that you’re on the Driver tab and if you are not, just navigate to it then click the Roll Back Driver button to switch back to the previous version of the NVIDIA Drivers.
Now restart your computer to successfully apply the changes made.

Option 4 – Try to run System Restore

You could also run System Restore as it might help fix the error code 0x0001 in NVIDIA GeForce Experience.

Tap the Win + R keys to open the Run dialog box.
After that, type in “sysdm.cpl” in the field and tap Enter.
Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
After that, follow the on-screen instructions to finish the process and then restart your computer and then check if the error code 0x0001 in GeForce Experience is now fixed.

Option 5 – Do a clean install on the NVIDIA driver

Before you do a clean install on the NVIDIA driver, you have to download the latest version of the Display Driver first.
Boot your Windows 10 PC into Safe Mode.
After that, double click on the executable file of the Display Driver Uninstaller to run and install it.
After the installation, open the program. Once you do, you should see the following window on your screen:
In the program window, click on the “Clean and restart” button.
After your PC has rebooted, download the NVIDIA drivers.
Then select your Product Type, Product Series, Product, Operating System, and Language appropriate for your hardware specifications as well as personal requirements.
Next, click on Search to display the latest available driver as per the information you entered.
And click on Agree and Download to start downloading the latest driver executable file.
Run the executable file after you finished downloading the latest driver executable file and then select Custom and click on Next.
Afterward, select “Clean Install” and proceed. Doing so would install the latest driver on your PC.
Restart your PC and check if the error’s now fixed. If not, you can try installing an older version of the driver instead.

Attempt was made to reference a token

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.

Option 1 – 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 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.

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

Note: Replace “[DLL file]” with the name of the DLL file that was pointed out in the error.

After you execute the given commands, you should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. After that, try to install the program again and see if it now works.

Option 2 – Replace the DLL file from a trusted source

First, you need to get the new DLL file from another computer with preferably the same file version number.
After that, you need to boot your PC into Safe Mode and navigate to the paths listed below and then replace the file using a USB drive or other external storage devices.
- x86: This PC > C:/Windows/System32
- x64: This PC > C:/Windows/SysWOW64
Next, type “cmd” in the Cortana search box and right-click on Command Prompt, and select “Run as administrator” to open it with administrator privileges.
Now type the “regsvr32 ntdll.dll” command and hit Enter.
Restart your PC and check if the error is now fixed.

Option 3 – Perform a System File Checker scan

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.

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.