iPhone Connects/Disconnects When Plugged In

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.

Seeing a yellow triangle with an exclamation mark on the battery symbol on the System Tray of your Windows 10 laptop is not really uncommon especially if your battery is about to run out of power. However, if you just purchased your laptop recently and the first thing you’ve noticed when you first opened it is the yellow triangle with an exclamation mark in the battery, read on as this post will help you resolve this issue. Seeing this kind of icon on your computer does not necessarily mean that you have to replace your battery as there are still several potential fixes you can try to resolve the problem. So if you notice this icon, you can try running the Power troubleshooter as it will help you resolve any potential issues with the battery. Aside from that, you can also restore the default settings of the power plan manually or uninstall and reinstall the battery driver. For more information, refer to the given options below.

Option 1 – Try to run the Power troubleshooter

As pointed out, the Power troubleshooter can help you resolve any issues your battery might have automatically. It plans and detects system settings that can affect power usages like timeout and sleep settings, display settings, and screensavers and restores them to their default settings. To run this troubleshooter, follow these steps:

• Open the Windows Settings and go to the Update and Security option.
• Next, click on the Troubleshoot option under Update and Security and then scroll down until you see the “Power” option.
• Under Power, click on the “Run the troubleshooter” button to start running the Power troubleshooter.
• Wait for a couple of seconds until the Power troubleshooter is done scanning your computer for issues. Once it’s done, follow the next on-screen instructions that appear on the screen.
• If needed, restart your computer and see if it has fixed the problem.

Option 2 – Restore the default settings of the Power plan manually

• Open the Windows Settings again and select System.
• Next, scroll down until you see the “Power & sleep” option.
• After that, click on the “Additional power settings” option located in the right pane to open the Power Options.
• Now click on the link that says, “Change Plan Settings” and select the “Restore default settings for this plan” option.

Option 3 – Try to uninstall or reinstall the Battery driver

You might also want to uninstall or reinstall the battery driver as it can also resolve the problem. But before you start, you have to shut down your computer and remove the power chord as well as the battery. Once you’re done, follow these steps:

• Plug the power chord and restart your computer.
• Once your computer has restarted, tap the Win + R keys to open the Run utility and type “devmgmt.msc” in the field and tap Enter to open the Device Manager.
• After that, look for the “Batteries” driver from the list of drivers and expand it.
• Then right-click on the “Microsoft ACPI-Compliant System” driver and click on the “Uninstall device” option.
• Once it’s done, restart shut down your computer and remove the power chord and then attach the battery.
• Now attach the power chord again and restart your computer to automatically install the driver.

If Error Code 0xc00000e9 appears on your screen, there is no cause to panic yet as there are different ways to fix this. Here, I will list down different methods to get your computer back on track:

1. Check peripheral connections
2. Check your SATA cables
3. Check your hard drive
4. Check your BIOS settings

Quick Fix 1. Check Peripheral Connections

1. Turn off your computer.
2. After the computer has been shut down, take off all the peripherals or the USB cables that are connected to your USB ports. This includes even the keyboard and the mouse. We just need to have only the monitor plugged in for this one.
3. Turn on your computer and see if it starts as it normally does.
4. If it does, try connecting back your external devices or peripherals one by one until you find the one that causes the error.
5. Once you trace the device that’s causing the error, you will have to change its USB cable and update its driver to support your operating system.

Quick Fix 2. Check your SATA cables

It is possible that what causes a barrier between your operating system and your hard drive from communicating is the SATA cable used. For example, if you’re using an older SATA with a SATA III port, there might not be adequate support for the transfer of data from one another. Or, the problem might be a loose SATA cable which would still require you to buy a new one to replace your loose or damaged cable. To check if your SATA cables are causing the error, simply follow these steps:

1. Turn off your computer.
2. Carefully open its case.
3. Check the hard drive and the SATA port where it’s connected.
4. Try to use a newer cable and connect it to your SATA port. (If you used a SATA II cable, you can see if a SATA III cable is more compatible.)
5. Replace your SATA cable with a newer one if Step 4 proves to be successful.

Quick Fix 3. Check your hard drive.

1. Try to use a different hard drive and see if error code 0xc00000e9 still appears.
2. If it works out just fine, then the problem might be physical damage to your hard drive and would need to be repaired depending on the case. Just simply take it to a technician and let him know about the issue.

Quick Fix 4. Check your BIOS settings

1. Restart your computer.
2. Once your computer starts, press and hold the ESC, F2, F12, or DEL key to go to BIOS settings.
3. You will then be redirected to the BIOS Setup Utility screen. From here, go to Boot options.
4. In the Boot Options, see if your first boot device is your hard drive. If it isn’t, press the arrow key to select the hard drive and move it to the top of the boot device list.
5. Save the settings.
6. Reboot your computer.

Note: If all the methods above do not work, the problem might be on your drivers and you might need to update them. You can update your driver in two ways: Manual driver update and Automatic driver update. You can find procedures online in updating your drivers.

One of the preferred ways to upgrade Windows 10 is by creating a bootable USB drive. However, you might change your mind when you encounter an error during the Windows 10 Setup that says, “We can’t find a USB flash drive”. Worry not for this error can be fixed using some suggestions that will be provided in this post. The funning thing about this error in Windows setup is that the computer says it’s not there when it’s clearly there. To fix this problem, you need to check if the USB device is accessible on your computer or you can also try a different USB device. In addition, you could check if there are any issues with both the USB 3.0 and USB 2.0 ports as it could be the reason why you’re getting the error or fix the bad sectors in the USB drive as well as see if the USB drive is set as the primary drive.

Option 1 – Try to check if the USB is accessible on your PC

The first thing you can do to resolve the problem is to check if you can access your USB device from your computer. All you have to do is open File Explorer and check if the USB device is listed there or not.

Option 2 – Try to connect a different USB device

The next thing you can do to fix the error is to try connecting a different USB device, specifically the one that has more significant storage space. You also have to make sure that it’s working on a different PC.

Option 3 – Fix any issues with the USB 3.0 and 2.0 ports

Although the USB 3.0 ports are compatible with the USB 2.0 ports, it does not necessarily mean that there wouldn’t be any problem when you use them which is why it’s best to fix any issues in them or better yet, use a compatible drive.

Option 4 – Try to fix the bad sectors in the USB drive via CHKDSK

When it comes to some issues concerning the hard drive or removable devices, there is a utility in Windows that might help which is called “chkdsk”. To use it, follow the steps below.

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

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

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

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

Option 5 – Try checking if the USB is set as the primary drive

You might also want to check if the USB drive is set as the primary drive because if it is, then it won’t appear on the list. It could also be that the USB drive has a primary disk in it. To undo it, you need to use the DISKPART utility.

• In the Start Search, type “command prompt” and right-click on Command Prompt from the search results, and then select the “Run as administrator” option.
• Next, execute the “diskpart” command to initiate the DISKPART utility.
• After that, type the “list disk” command and tap Enter to display the list of disks on the computer. You have to take note of the drive number or letter of the concerned USB drive.
• Once done, type the “select disk <X>” command where X is the drive letter or number and tap Enter.
• Then execute the “list partition” command to see the list of all the partitions in your computer. It should be listed as 0, 1, or 2. 0 is the primary partition.
• Now type the “select partition 0” command and tap Enter and then type “delete partition” to delete the selected partition.
• You can do the same to the other partitions as well and when you’re done, execute the format command to turn the USB drive into a standard one.

You will notice the blurred background on the login screen right away when you start your Windows 10 computer that’s running the v1903 and up. This kind of blurred background is known as “Acrylic Blur Effect on Sign-in Screen”. This new feature delivers a beautiful experience to users by adding more focus to the login screen. However, no matter how nice this feature is and even if it only stays for less than a minute, not all users like it and if you’re one of these users, read on as this post will guide you in disabling the blurred background login screen in your Windows 10 computer. Disabling the blurred background in the login screen can be done in two methods. The first one is via the Registry Editor and the second one is via the Group Policy Editor. Before you proceed, make sure that you are using an admin account and you must create a System Restore point first. Once you have that covered, follow the options provided below.

Option 1 – Disable the Blurred background in the login screen via Registry Editor

• First, tap the Win + R keys to open the Run dialog box and type “Regedit” in the field, and hit Enter to open the Registry Editor.
• After that, navigate to this registry path: KEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsSystem
• Next, right-click on any empty space in the right pane and create a new DWORD (32 bit) and name it as “DisableAcrylicBackgroundOnLogon”.
• Once you’ve created the DWORD, double click on it and set its value to 1 to disable it and 0 to enable it.
• After you make the necessary changes, restart your computer. You won’t now see the blurred background on the login screen.

Note: No matter what option you select to change the background, it will stay blurred when you click on the login button. At the time of writing, there is no way to disable this feature in the Personalization section so the Registry Editor will have to suffice for now.

Option 2 – Disable the Blurred background in the login screen via Group Policy Editor

• Tap the Win + R keys to open the Run utility and type “gpedit.msc” in the field and tap Enter to open the Group Policy Editor.
• After that, navigate to this policy setting: Computer ConfigurationAdministrative TemplatesSystemLogon
• From there, double click on the “Show clear logon background settings” and since its default value is “Not configured”, set it to “Disabled”. You will see the following description under this setting:
  • “This policy setting disables the acrylic blur effect on the logon background image.”
  • “If you enable this policy, the logon background image shows without blur.”

• Now click on OK and then check the login screen.

Note: If you don’t configure or if you disable this policy, the logon background image adopts the acrylic blur effect. However, if it didn’t work, you have to restart your computer and then check.

The author of the famous software library mode-ipc that gets over a million downloads per week found that it has some questionable code inside. The code itself behaves like this: if it finds out that your location is within Russia or Belarus it will try to replace the contents of all files on the computer with a heart emoji.

One important thing is that we here are not supporting the current Ukrainian situation and are against any type of violence or war but we also do not support this kind of behavior as well. If we look at this only from a technical perspective, we would then classify the mode-ipc library as malware and a harmful piece of code no matter the motivation behind it.

So this so-called protestware is well basically malware, but not always, it will protest when certain conditions are met. The issue with this is that companies and users should not be placed under harm if they do not share the personal view of the code author. Imagine if, for example, I would publish code to delete all pictures from your computer if my code found out that you do not like metal music. I guess you not liking metal music and war in Ukraine are two very different things but the source is the same, unreliable code that invades your privacy in order to serve one purpose, punishment for disagreeing with my personal views and that should not be allowed.

Not all protestware are equal, some will not harm your computer on purpose, they will just annoy you with some messages like viruses did in their infancy stages, others might place some developer sanctions but no matter the outcome basic principle is the same, it does something without user consent and without informing the user that something like that might happen.

On the internet, many blog posts and discussions were open about this issue and its morality. Discussion is still active with different takes on the situation and how to prevent it. Our take on this matter is that professional developers should have standards and not submit to doing harm for the sake of personal views and feelings.

In the long run, this kind of behavior and practice can only harm developers involved in this kind of entanglement. Infected libraries will in time stop being used since people would not trust them and authors will have a stain on their name as impulsive or not trustworthy.

Hive ransomware has been targeting Microsoft exchange servers lately vulnerable to ProxyShell security issues in order to deploy various backdoors. Once the backdoor has been placed various attacks can be performed including but not limited to network reconnaissance, stealing admin accounts, taking valuable data, and even installing and deploying file-encrypting algorithms.

ProxyShell wide abuse

ProxyShell is a set of three vulnerabilities in the Microsoft Exchange Server that allows remote code execution without authentication on vulnerable deployments. The flaw has been used in past by various ransomware like Conti, BlackByte, Babuk, Cuba, and LockFile.

Security vulnerabilities have been reported to be fully patched on May 2021 but how Hive was able to still be successful in exploiting PowerShell and infiltrating into the system there seems to be still some unpatched and open issues.

Hive

Hive has gone a long way since it was first observed in the wild back in June 2021, having a successful start that prompted the FBI to release a dedicated report on its tactics and indicators of compromise.

In October 2021, the Hive gang added Linux and FreeBSD variants, and in December it became one of the most active ransomware operations in attack frequency.

Last month, researchers at Sentinel Labs reported on a new payload-hiding obfuscation method employed by Hive, which indicates active development.

As you know, System Restore is a useful tool in Windows operating system that helps users in fixing system issues by undoing any recent changes to the computer that may have caused the problem. However, there are times when you might encounter some issues when running this tool and one of these issues is when System Restore suddenly gets stuck or hangs up on initializing the restoration of the Registry in Windows 10. If you encounter a similar problem, read on as this post will guide you on what you can do in such cases. There are several things you can do when you face this kind of problem in System Restore. First, you can try to wait it out, give it more time to load, which should not take longer than 5 minutes. And if it’s still stuck after that time, give it another hour. However, if nothing changed after an hour, then you need to troubleshoot the problem further. Keep in mind that you must not interrupt System Restore by shutting it down abruptly, it could result in an unbootable system. To get started in troubleshooting the problem, you need to follow each one of the suggestions offered below.

Option 1 – Try to use the Windows Recovery Environment

The first troubleshooting option you need to try is to simply tap the power button for about 10 seconds. This is what you have to do when you have to interrupt System Restore or reset your Windows 10 computer. Tapping the power button for 10 seconds will perform a hard shutdown and once your computer shuts down, restart your computer again and follow the steps below but before you do that, make sure that you have a Windows bootable USB or DVD.

• First, insert the bootable USB or DVD and boot into it, and select the “Repair your computer” option.
• Next, once you see the manufacturer logo on your computer, tap the key to enter into Windows Recovery Environment.
• After that, change the Boot sequence to DVD drive under the UEFI Firmware settings and restart your computer.
• Once your computer has restarted, select the boot order and make changes accordingly as displayed in the BIOS.

Option 2 – Try to run the Automatic Repair Utility

You might also want to use Automatic Repair in fixing the error. To do so, follow the steps below.

• You can start by creating and booting from a bootable Windows 10 USB Stick.
• After that, click on Repair your computer located on the bottom left corner when you are on the initial Windows Startup screen.
• Next, click on Troubleshoot, and then on the other screen, click the Startup Repair option.
• Now select the operating system you want to repair. Once you do that, it will start to repair your operating system. Wait until the process is completed and then check if the problem’s now fixed.

Option 3 – Try to run System Restore in Safe Mode

If you can’t boot into your Windows 10 computer, you can try to run System Restore again in the Advanced Startup Options.

• Boot your computer into Safe Mode.
• After that, select an option > Troubleshoot > Advanced Options > Startup Settings > Restart.
• Once your computer has restarted, tap the F6 key to enable Safe Mode with Command Prompt and to run System Restore from there.
• Now in Command Prompt, type the “rstrui.exe” command to run System Restore in Safe Mode. This will help in fixing the problem since it would be safer to perform System Restore of the computer.

Error Code 0x80070422 - What is it?

Error Code 0x80070422 can be found on many versions of the Windows operating system including Windows 7, Windows 8, and 8.1, and Windows 10. The reason for its occurrence may vary, however, depending on the version of the operating system that you use.

In the case of error code 0x80070422 in Windows 8, it often occurs when users attempt to update their firewall or download apps from the Windows store. When this error occurs the user is unable to complete the updates and will need to apply different solutions to correct the issue.

Solution

Error Causes

Whenever error code 0x80070422 is encountered on Windows 8 or 8.1, it might be a result of various factors. These error codes include:

• Registry errors – This occurs when new programs are installed over old ones
• Malicious software such as adware, spyware, and or viruses

Further Information and Manual Repair

You do not need to be a Windows expert to attempt to solve errors like the 0x80070422 Windows 8 error code. Simply try the solutions below. If however, you feel you need a professional’s help, contact a certified Windows technician.

• Check for any viruses or malicious software

Viruses and other malicious software are often the cause of various issues within the PC. For this reason, be sure to check your machine for a possible virus infestation. If you are unable to use your anti-virus software or if none is present you might need to download an automated tool that offers overall repair and other solutions.

• Disable third-party security apps

Another step you can take is to disable third-party security apps. When these apps are downloaded onto your device, it can lead to the disabling of your Firewall and the inability of your device to download other apps. If this is the source of the 0x80070422 error code on your machine, the issue will be resolved after you disable the third-party apps and reboot your computer.

• Disable Firewall

If error code 0x80070422 in Windows 8 or 8.1 occurred while you attempted to update Windows firewall, one of the best solutions you can try is to disable the firewall. Note however that disabling your firewall should be temporary as it protects your computer from worms as well as hackers that might infect or compromise your PC. Access the firewall by swiping right on the screen then searching for “firewall”. Click “Windows firewall” then select “Turn off Windows firewall”.

• Performs a clean boot

Another option is for you to perform a clean boot. This simply refers to a reboot in Windows where only a minimum set of drivers and programs are used. A clean boot can help resolve issues related to software conflict which can occur when Windows users install programs or updates or simply run a program. Note that you must log on to the computer as an administrator. Otherwise, you will not be able to perform the clean boot.

• Clean registry

The source of many errors related to Windows can lie within the registry. This is because the registry is involved in every aspect of a Windows computer’s operation. If there is an issue in the files of the registry or if it has been hacked, your computer will not function. For this reason, begin by cleaning the registry regularly. To clean our registry, use a powerful tool that is both reputable and user-friendly. Research your option before you make a selection as choosing the wrong tool could lead to even more errors or computer malfunctions.

• Set Windows Update to Automatic

Another important method to solve issues related to error code 0x80070422 in Windows 8 or 8.1 is your Windows Update service. Though you may have never noticed this feature before now, the Windows Update services allow PC owners to access updates to their operating system automatically. This leads to a properly functioning PC as your machine will always have the latest features and tools available. However, if the setting is not correct, your computer may end up experiencing error code 0x80070422. Check if this is the source of your problems by verifying if your Windows Update settings are automatic. Once the settings are on automatic, reboot your machine to ensure your computer responds to the changes.

• Download an Automate Tool

Always be prepared for the possibility of other errors. You can do this by downloading powerful software. This enables users to regularly check for issues that may cause errors on their Windows device.

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.