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

Error CausesHive 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 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 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.
Users, when upgrading to Windows 10 from Windows 7 or Windows 8/8.1, or when upgrading to a new version, build, service pack, or major update of Windows 10, can encounter error code 0xC1900101, 0x30018. Windows 10 installation fails and stops or hangs. During the installation process, it will reach a certain maximum limit (normally at 6% or 32%) then reverts back to the previous version of the operating system and displays the following message:
We couldn’t install Windows 10. We’ve set your PC back to the way it was right before you started installing Windows 10.
0xC1900101 – 0x30018 The installation failed in the FIRST_BOOT phase with the error during the SYSPREP operation.
Error CausesIn attempting to fix Error Code 0xC1900101-0x30018, it is vital to know what causes this issue. The most probable causes of this error are:
NOTE: If this fails, if possible, you can try using the .ISO file in upgrading.
If you’re using Windows Update in installing Windows 10, you can implement the following:
NOTE: Don’t forget to hit Enter after every command.
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
NOTE: Don’t forget to hit Enter after every command.
ren
C:WindowsSoftwareDistribution SoftwareDistribution.old
ren
C:WindowsSystem32catroot2 Catroot2.old
NOTE: Don’t forget to hit Enter after every command.
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
Jokes aside, I truly believe that choosing to upgrade your System to Windows 11 at this point in time is a bad decision and I will explain why I do believe it.
“Your PC ran into a problem and needs to restart. We’re just collecting some error info, and then we’ll restart for you. (100% complete) If you’d like to know more, you can search online later for this error: DRIVER_IRQL_NOT_LESS_OR_EQUAL (wrUrlFlt.sys)”The iaStorA.sys file is a software component that’s related to the Intel Rapid Storage Technology by Intel. It is a software solution supported by Intel Smart Response Technology which allows the PC to communicate with the hardware as well as externally connected devices. The Intel Rapid Storage Technology enables the Peripheral Component Interconnect Express or PCIe storage support, serial ATA RAID or Redundant Array of Independent Disks 0, 1, 5, and 10 support, and the PUIS or power-up in standby is also supported. To resolve this kind of BSOD error, you have to update, roll back or fresh-install the problematic driver. Refer to the options laid out below for detailed instructions.
“There were problems installing some updates, but we’ll try again later. If you keep seeing this and you want to search the web or contact support for information, this may help: 2018-03 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4088776) – Error 0X800F0900”This kind of Windows Update error is most likely caused by some corrupted files in the system. It is also possible that the Windows Database might have become corrupted as well. So if you are currently experiencing this problem, refer to the options given below and see which one of them works best for you.
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindows /LimitAccess
net stop wuauserv net start cryptSvc net start bits net start msiserver
net start wuauserv net start cryptSvc net start bits net start msiserver
Buzzdock is a browser extension. Buzzdock will be automatically enabled on IE and Chrome following installation, and you may begin using Buzzdock with no further action required. If you elect to optimize Buzzdock performance, the settings preferences of your browser may be adjusted after installation. This browser extension changes your default search provider to Buzzdock.com custom search. It displays additional unwanted ads, banners & sponsored links on web pages that you visit, and it hijacks your browser home page. This browser extension has been flagged as malware by many anti-virus scanning programs.
So, what is Electron bot, and why it even matters if it is in the MS store. Electron bot is malware that somehow found its way inside MS Store via game clones of popular games temple run and subway surfer. This infiltration led to the infection of around 5000 systems over the globe in a very short period of time.

This malware is a backdoor that gives complete system control to the attacker. Any type of execution can be performed remotely in real-time. Usually, this kind of attack was aimed at a spread of click fraud over popular social media like Facebook, google, youtube, etc.
Electron Bot's primary goals in the ongoing campaign analyzed by researchers are:
These functions are offered as services to those who want to increase their online profits illegitimately, so the gains for the malware operators are indirect.
For now, users may take note of the publishers who released confirmed malicious game apps using the following names: