The quick demise of the BRAVE browser

You might be trying to play music files using the Windows Media Player, but were unable to do so since you encountered an error saying, “Windows Media Player Error – Server Execution Failed” error. If you encountered this error, worry not for this post will guide you on how to fix it using some potential fixes. In the error message, the “Server execution failed” indicates that the “wmplayer.exe” is still running or shutting down at that point and it is possible that it is stuck which is not able to close properly. To fix this error, there are several potential fixes you can try. The first one is to run the Video Playback troubleshooter. While you could also try to disable the WMP Network Sharing Service or register both the jscript.dll and vbscript.dll files. For more information, refer to the options provided below.

Option 1 – Try to run the Video Playback troubleshooter

The first thing you can do to fix the problem, you can try to run the Video Playback troubleshooter instead. To run it, simply go to Settings > Update & security > Troubleshoot. From there, scroll down until you see the Video Playback option and then click on the “Run the troubleshooter” button to get started. This troubleshooter will detect and automatically fix any problems related to video playback so it should help fix the error.

Option 2 – Try to disable the WMP Network Sharing Service

If the Video Playback troubleshooter didn’t work in fixing the problem, the next thing you need to do is disable the Windows Media Player Network Sharing Service. The WMP Network Sharing Service is used to share the libraries of the Windows Media Player to other users on the network as well as media devices using the Universal Plug and Play. And since you are not using any network here, then you can disable this service to fix the problem. How? Refer to the given steps below.

• Tap the Win + R keys to open the Run dialog box and type “services.msc” in the field and tap Enter to open the Services Manager.
• Next, look for the Windows Media Player Network Sharing Service from the list of Services and right-click on it.
• After that, click on the Stop option and see if it fixes the Windows Media Player error.

Option 3 – Try to register the jscript.dll and vbscript.dll files

• Tap the Win + X keys and from the menu select the Windows PowerShell (Admin) option to open an elevated Command Prompt.
• Next, type this command to register the jscript.dll file and click on the confirmation box: regsvr32 jscript.dll
• After that, execute the regsvr32 vbscript.dll command to register the vbscript.dll file.
• Once you’re done, these DLL files will be re-registered and should fix the Windows Media Player error.

The NVIDIA Control Panel is a useful tool for users who have NVIDIA graphics on their PCs as this tool allows users to how the graphics card is used on the computer using several controls that come with the graphics card from NVIDIA. Thus, it can be quite inconvenient when it suddenly crashes all of a sudden for some reason. This kind of problem could be due to the toggling of Output Dynamic Range is limited, or there could be some issue with the integrity of the Power Supply for the graphics card, and many more. So if you are using NVIDIA on your computer and its Control Panel keeps on crashing on your Windows 10 computer, then you’ve come to the right place as this post will guide you in sorting the problem out. For more details, refer to the guidelines laid out below.

Option 1 – Try to toggle the Output Dynamic Range

The first thing you can do to fix the problem is to toggle the Output Dynamic Range by following these steps:

• Navigate to this path: Display > Change resolution.
• Next, scroll a bit on the right-side panel until you see the Output Dynamic Range drop-down.
• After that, select “Full” from the drop-down menu.
• Apply the changes you’ve made and see if it is able to fix the problem with the NVIDIA Control Panel.

Option 2 – Try changing the Power Management and Vertical Sync settings

The next thing you can do to fix the problem is to change the Power Management, as well as the Vertical Sync settings.

• Open the NVIDIA Control Panel and go to this path: 3D Settings > Manage 3D Settings.
• Next, set the Power Management to be “Prefer Maximum Performance” for your processor located on the right-side panel.
• After that, set the Vertical sync setting off and then click on the Apply button located at the bottom-right portion of the window and check if it is able to fix the problem or not.

Option 3 – Try updating the drivers from the official site of NVIDIA

If both the first and second given options didn’t work, you can also try updating the drivers from the official NVIDIA website. And in case you don’t know the type of Nvidia graphics card that your computer is on, 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.

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

The Event Viewer in the Windows operating system is used to troubleshoot any computer issues. It is one of the most useful tools that keep logs of both security and system events. It also monitors for both software and hardware problems in the computer. This tool is the only one with amazing features that maintain logs about everything that’s going on in the computer system. It keeps track of all the information to the point where going over them will take a lot of time. Luckily, the Event Viewer tool now allows users to create custom views where you can set the filters and sort the data recorded to limit the information details to only what you’re interested in seeing. For instance, if you want to troubleshoot with one hard drive, you can just create a special custom view to display only the hard drive warnings in the security logs. This will save you hassle and time. Take note that the logs in the Event Viewer are divided into two main categories namely the Window logs and the Application and Services logs. You can just set the filter to the logs by their event id, specific date, and many other events when you have to troubleshoot some problem in your computer. So if you are trying to troubleshoot a problem in your Windows 10 computer and you’re checking the Event Viewer, read on as this post will guide you in creating custom event views in the Event Viewer. To get started, refer to the instructions given below. Step 1: Go to the Start menu and in the search box, type “event viewer” and then click on Event Viewer from the search results to open it. Step 2: After opening Event Viewer, click on Custom Views located in the left pane of the window. Step 3: Next, click on the Administrative events under the Custom View to create special log views. Step 4: Then on the right side of the window, click on Create Custom View to open the Create Custom View window. Step 5: There is a logged drop-down list under Filter. From there, you have the option to choose an appropriate predefined time or use a custom time range for your Custom log views. Step 6: After that, select an appropriate event level for your custom view. You have fine entry-level options to choose from such as critical event level, error, warning, information and verbose.

• Critical – select this if you want to see the events that require your immediate attention in the custom view.
• Error – select this if you want your Event Viewer to display the events that are less critical but hints at the problems.
• Warning – select this event-level if you want to see the event with the potential problem but may not bound to happen.
• Verbose – select this if you want to see detailed information about all the events.

Step 7: After you’ve selected the event level, you now have to select how you want the events to be filtered. They can either be filtered By the log or By the source.

• By the log – you can select two options called Windows log and, Application and Service logs. The Windows logs allow you to filter the logs created during events like setup, security, applications, and system events. While the Application and Service logs filter the log created by the installed applications in your system.
• By the source – select this if you want your Custom View to search for information in event sources. It allows you to view events in detail for various applications and devices.

Note: You have the option to further customize the event logs with more filters like Event IDs, task category, keywords, User, and Computer. Using these additional filters, you can choose to filter the events in the special views by specifying event id numbers in the Event IDs, entering predefined Windows words in the Keyword, specify the user accounts in the User field, as well as choose the system from the server to maintain logs in the Computer field. Step 8: Once you’re done customizing the log filter, click on OK to apply the changes made. Step 9: After that, a Save Filter should be displayed in the Custom View window. Just enter the Custom View name and select the Event Viewer folder where you want to save the Custom view. The folder name should be Custom View by default. And if you want, you can also create your own folder if you want your custom views to be visible to all the system users. Step 10: Next, check all the Users box located in the lower corner of the window and then click the OK button after you’re done. You should now see the customized filter you just created on the left side of the window. Just click on it to check your filtered events in the center of the Event Viewer window. And for you to save the custom view logs, simply right-click on the Custom views you created and then click on Save All Events in the Custom View As from the drop-down menu. Then put a name on the file and select the appropriate location where you want to save the logs and click on the Save button. Note that the log file is saved with the “.EVTX” file extension and when you double click on it, it will open the file in the Event Viewer.

If we are to believe news from Intel, new series of processors based on Alder Lake architecture are about to be released somewhere in October. Alder Lake is the 12^th Generation Core of Intel processors and it is meant to have all advantages of the current CPU structure. I9 is aimed to pack a punch against its competitors with technology including eight high-performance Golden Cove cores (P-cores) with Hyper-Threading and eight energy-efficient Goldmont (E-cores) equipped with a 30MB L3 cache and operating at high clock speeds. During the benchmark test, the new CPU outperformed all of Intel’s previous Rocket Lake structure processors which is logically expected but the big surprise came from results that indicate better performance than Apple’s new M1 processor even in single-threaded performance which is supposed to be best in that field. Another surprise was really beating AMD Ryzen 9 in each field. If we take into account that i9 has 16 cores in total and can process 24 threads against Ryzen 9 with 16 Cores and 32 threads this is an impressive feature. Now truth to be told Alder lake has massive L3 cache and microarchitectural advantages and consumes much more power but the results of performance are high. Also, note that this early CPU is not really a mass production one and maybe some things will still change but early results are very satisfactory. We will see what will price tag be since in this age of shortage and competition that will also play a big role in its overall success. Speaking of competition I eagerly await AMD’s response to this, in any way it seems that the CPU market is for some turbulence which is always a good thing for the final customer and I welcome it.

One of the useful features that came with Windows 10 is the Mobile Hotspot although there’s a downside to it – it drains your battery faster especially if your Windows 10 device is running on battery. Another one of its flaws in the implementation of this feature is that it stays activated even when the connection is idle. In other words, it is still activated even if no devices are connected to it. As a result, it consumes battery life and affects it. There are also instances when it affects the performance of the network connection. At the time of writing, Microsoft hasn’t done anything about this dilemma yet so in the meantime, you can continue reading this post to resolve this issue on your Windows 10 device. You can remedy this Mobile Hotspot issue by running a command in Windows PowerShell. To get started, follow the given instructions below.

Turn off Mobile Hotspot Automatically:

Step 1: The first thing you have to do is to copy the following command:

powershell -windowstyle hidden -command "Start-Process cmd -ArgumentList '/s,/c,net stop "icssvc" & REG ADD "HKLMSYSTEMCurrentControlSetServicesicssvcSettings" /V PeerlessTimeoutEnabled /T REG_DWORD /D 1 /F & net start "icssvc"' -Verb runAs"

Step 2: After copying the command given above, open the Notepad app and paste the command you copied there and save it. And when saving it, select the “Save as” option and its File type as “All files”. Step 3: After that, put “TurnOnTimer.bat” as the file’s name and save it on your Desktop. Step 4: Once done, run the file you just created, and when a User Account Control or UAC prompt appears, just click on Yes. Step 5: After you run the file, it will run a series of scripts in a command line which will turn off the Mobile Hotspot automatically when idle. And that’s how you automatically turn off the Mobile Hotspot when your Windows 10 device is idle. On the other hand, if you want to undo the changes made, you can always do so using the steps provided below.

Turn on Mobile Hotspot:

Step 1: Copy and paste the following command in the Notepad app:

powershell -windowstyle hidden -command "Start-Process cmd -ArgumentList '/s,/c,net stop "icssvc" & REG ADD "HKLMSYSTEMCurrentControlSetServicesicssvcSettings" /V PeerlessTimeoutEnabled /T REG_DWORD /D 0 /F & net start "icssvc"' -Verb runAs"

Step 2: After copying and pasting the command, save it as “TurnOffTimer.bat” on the Desktop. Step 3: Once done, run the file like what you did earlier and select Yes when a UAC prompt pops up. This will run a series of scripts on a command line which will revert the changes back to their default state.

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:

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

1. 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.
2. 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.
3. 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.

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

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

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

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

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

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.

One of the most useful utilities for advanced users in Windows is the Windows command line or Command Prompt. It is efficient in fixing system files, checking the disk for errors as well as other intensive tasks that are made convenient using this. One of the tasks you can carry out using Command Prompt is repairing the Windows bootup process if it encounters any issues. However, if you tried running the “bootrec/fixboot” command and you receive an error message saying, “Element not found”, read on as this post will guide you in fixing this error. This kind of error in the command line could be due to a damaged BCD or MBE, inactive system partition, or it could also be that there is no drive letter being assigned to the EFI partition. Whichever the case is, here are some possible fixes that should help you resolve the problem.

Option 1 – Try to repair BCD

As mentioned the error could be caused by a damaged BCD and so to fix the problem, you need to repair BCD by following these steps:

• First, make sure that you have a bootable Windows 10 USB drive with you and use it to boot your computer.
• Once you’re on the Welcome Screen, click on Next.
• After that, click on Repair your computer located at the bottom-left portion of the window.
• Then select Troubleshoot > Advanced Options > Command Prompt.
• After you open the Command Prompt window, execute the following command:

bootrec /fixboot

• Afterward, enter the next command below to rename the BCD file:

ren BCD BCD.bak

• Next, type the following command and make sure to replace “b:” with the letter of your bootable drive attached to your computer.

bcdboot c:Windows /l en-us /s b: /f ALL

• Now, wait until the process is completed and restart your computer to successfully apply the changes made.

Option 2 – Try assigning the drive letter to the EFI partition

• Tap the Win + X keys or right-click on the Start button and click on Command Prompt (Admin) to open Command Prompt with admin privileges.
• Then type the following command to start the Diskpart utility:

diskpart

• After that, if you receive a UAC prompt, just click on Yes to proceed.
• Next, type the following command to list all the volumes created on your PC including both types of partitions that are visible to a normal user in the File Explorer as well as the ones created by Windows 10 by default which helps it in storing the boot files and other important system files:

list volume

• Now type the following command to select the desired volume:

select volume number

• Then type the following command to assign a letter to the selected volume:

assign letter=<LETTER>

Note: Make sure to replace “<LETTER>” with the letter you want to allocate to that partition. Afterward, it will assign a letter to the selected volume.

• Reboot your PC to apply the changes made.

Option 3 – Try setting the System Partition to Active

Like the first given option, you also have to make sure that you have a bootable Windows 10 USB drive before you proceed to set the System Partition to Active. Once you have it covered, refer to these steps:

• Boot your computer using the bootable Windows 10 USB drive.
• Next, click Next when you get to the Welcome Screen.
• Then click on Repair your computer located at the bottom left part of the window and select Troubleshoot > Advanced Options > Command Prompt.
• After opening Command Prompt, type the following command and hit Enter to start the Diskpart utility. It is a command line-based utility just like Command Prompt but has a UAC prompt once you provoke it. So if you encounter a UAC prompt, just click on Yes to proceed.

diskpart

• Now type the following command:

list disk

• From there, select your primary disk by typing the following command:

select disk number

• After that, list all the partitions on the selected disk by entering the following command:

list partition

• The command you just entered will list all the partitions created on your PC including both types of partitions that are visible to a normal user in the File Explorer as well as the ones created by Windows 10 by default which helps it in storing the boot files and other important system files.
• Now type the following command to select the partition that is usually around 100 MB in size:

select partition number

• Finally, type the following command to mark the partition active:

active

• Then type the “exit” command to exit the disk part utility.

From their infant stages to modern days, computer viruses were always kind of here. From simple ones that were annoying with playing speaker sounds and throwing messages on screen to more malicious ones capable of deleting and encrypting files. In today's modern world it is very important to protect yourself, modern viruses are not a joke anymore and they are aimed to create serious damage to computer systems. They can encrypt files in order to make you pay for a decrypter, they can straight up delete files or even cause some hardware damage. Like mentioned before protecting yourself is important, but protecting does not mean only having antivirus software installed, information, where are common places in which they lurk and could be picked up, is also very important. That is why we are exploring in this article the most common place where you can pick viruses or other malware.

Downloading Programs

Programs that contain the downloadable files are the commonest source of malware such as freeware, worms, and other executable files. Whether you download an image editing software, a music file, or an e-book, it is important to ensure the reliability of the source of the media. Unknown, new, or less popular sources should be avoided.

Pirated or Cracked Software

Are you aware of software cracking? Well, every time you open cracked software, your antivirus software might flag it as malware as the cracks consist of malicious scripts. Always say “No” to cracks as they can inject malicious script into your PC.

Email Attachments

Anyone can send you an email attachment whether you know them or not. Clicking on unknown links or attachments can harm your device. Think twice before clicking anything and make sure that file type is not ‘.exe’.

Internet

One of the easiest ways to get a virus on your device is through the Internet. Make sure to check the URL before accessing any website. For a secured URL always look for ‘HTTPS in it. For example, when you click videos published on social media websites, they may require you to install a particular type of plug-in to watch that video. But in reality, these plug-ins might be malicious software that can steal your sensitive information.

Booting Data from Unknown CDs

Malicious software can get into your device through an unknown CD. A good practice to be safe from malicious infection is to remove CD when your device is not working at all. Your system could reboot the CD if it is not removed before switching off the computer.

Bluetooth

Bluetooth transfers can also infect your system, so it is crucial to know what type of media file is being sent to your computer whenever a transfer takes place. An effective armor would be to allow Bluetooth connectivity with only known devices and activate it only when required.

Unpatched Software

Often overlooked, unpatched software is also a leading source of virus infection. Security holes in software are exploited by attackers and are unknown to software makers until the attackers release them in the form of zero-day attacks. It is therefore recommended to install software updates as soon as they are available on your PC.

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.

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.

Option 4 – Try reverting back to the previous build of Windows

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.