Fix Gah, Your tab just crashed in Firefox

The latest update from Panos Panay on Twitter is including New and redesigned Snipping tool inside Windows 11. From the shared video, we can see that it includes modern Windows 11 UI redesign and it looks and feels like a part of Windows 11. More things that can be seen from the shared video is that it looks like the new snipping tool is a merged version of the old with snip & sketch. It is good to see that it is still possible to capture screen with easier way natively inside Windows 11 but some more functionality would be more welcome I guess. Users were asking for added functions for a long time like adding simple text for example but from shared video, no new features were presented so for some users 3^rd party solutions will still be the way to go. The new and redesigned Snipping tool will roll out with the next update and we will see then about all new features inside it firsthand. Until then, take care.

There are a lot of online services and a lot of ways to get your public IP address. One of them being typing whats my IP in Google search and you will get immediate results. But there is a way to get the same information inside Windows 10 which could be very useful if for any reason you can not connect to mentioned services. By checking public IP directly inside your windows you can make sure that the issue for not being able to open some websites is not due to your public IP. In order to use this Windows feature, we will be checking our public IP using Windows PowerShell. To open Power Shell in Windows first press ⊞ WINDOWS + R to open the run dialog Inside run dialog type Powershell and press ENTER In the Powershell type in the following command and press ENTER

(Invoke-WebRequest -uri "http://ifconfig.me/ip").Content

When the command finishes you will see what is your public IP address, if you wish to know more about your connection type in and press ENTER:

Invoke-RestMethod -Uri ('https://ipinfo.io/')

This command will provide you with further information like city, region, country, and others.

If you were trying to copy, move modify or delete a folder or a file in your computer but you’re not able to do so and encountered an error instead that says, “Could not find this item, This is no longer located in <path>, Verify the item’s location and try again”, then you’ve come to the right place as this post will guide you on how you can fix this error. You can encounter this error when you delete, rename, open or copy a certain file which is often created by third-party software and lacks important information like file format, and so on. Although you can see these files in File Explorer, you might not be able to perform some operations in them. To fix this problem, you need to check out the given suggestions below.

Option 1 – Try to rename the file via Command Prompt

If you were trying to rename the file but unable to do so, you can achieve that by executing a command in Command Prompt. Make sure to follow the steps carefully.

• Type in “Command Prompt” In the Start menu to search for it or you could also click the search button right next to the Start menu and then right-click on the related result and select the option “Run as administrator” to open Command Prompt with admin privileges.
• Next, type in “cd” followed by the path where the file is located with this format – “C:/Folder1/Folder2/Folder3”. However, you have to omit the problematic file this time. To put it simply, the last folder in the command must be the folder where the file is located.
• After inputting the command, press Enter on your keyboard and then use the set of commands given below. Note that each command is a new line so you need to tap Enter after copying each line.
  • DIR /A /X /P
  • RENAME (the current name of the problematic file) (a non-problematic name)
  • EXIT

Note: Make sure that you only input the current name and the new name separated by a space. You must not write the brackets in the command. If everything goes well, you will now be able to operate the file like you used to before.

Option 2 – Try to delete the file using Command Prompt

On the other hand, if you were trying to delete the file instead of renaming it, you can execute another command in Command Prompt.

• Open Command Prompt with admin privileges like what you did earlier.
• Once you’ve opened Command Prompt, copy and paste the command given below and tap Entre after you do so. You also have to make sure that you key in the correct path where the file is located as well as its name.

rd /s \?X:badfolderpath

Note: In the command above, “X” is the placeholder letter so you must input the letter that corresponds to the drive’s letter where the file is located.

• After that, you will see the “Operation completed successfully” message on your screen. If you don’t, check if you’ve really inputted the correct location of the file or its name.

Option 3 – Delete the file without any extension

If the file you were trying to delete does not have an extension, this means that Windows does not know what to do with this file which is why it’s throwing an error message. The best thing to do in such cases is to delete the file especially if it takes up a lot of memory. To delete these kinds of files, here’s what you have to do:

• Follow the first two steps from the previous option above so you can navigate to the location of the file accurately just be careful in inputting the folders.
• Don’t forget to tap Enter right after each command and then use the next command below so you can delete the affected file which has no extension:

del *.*

• After you’re done, open the File Explorer and then check if the file is now deleted or not.

Driver Verifier is a built-in tool in Windows 10 that monitors device drivers on your computer, if it detects issues with drivers, it will attempt to fix the issue. If you are encountering Blue Screen for a Driver and after running Driver Verifier you get another with message DRIVER_VERIFIER_DETECTED_VIOLATION ten follow this article step by step in order to solve it. There is a chance that you will maybe even have to do this in safe mode, if that is your case, login into safe mode and proceed, otherwise proceed normally.

1. Update Device Drivers

   the most common issue with the blue screen is old Drivers, in most cases, graphical drivers, update all Drivers with the latest versions and see if this will resolve the issue.

2. Stop or uninstall Virtualization software

   Virtua machine software is a great way to have a safe environment and to experiment while preserving your Windows installation intact, however sometimes due to the nature of these applications they can be a case for blue screen errors. Stop virtualization software to see if it will remove the issue. If that is the case, try another virtualization application

3. Disable Driver Verifier

   Press ⊞ WINDOWS + X to open the secret menu Click on Command Prompt (admin) Inside command prompt type: verifier and press ENTER Select the Delete existing settings radio button Click Finish Reboot your computer

4. Reset Driver Verifier

   Press ⊞ WINDOWS + X to open the secret menu Click on Command Prompt (admin) Inside command prompt type: verifier /reset and press ENTER Reboot your computer

5. Use system restore

   Rollback Windows to the previous state where everything was working fine.

Hello and welcome everyone, today we will be talking about dreaded keyloggers, why they are dangerous, and how to know if you might have one in your system. Keylogger is a malicious application placed in your system and hidden with only one goal in mind, to get information about what are you typing and by that means for a person who infected you to get information about your credit card information or other sensitive data. They can be introduced into your systems in various ways and often can not be detected easily. Modern antivirus applications have ways of detecting them and removing but this tutorial aims to teach you how to spot them all by yourself since new keyloggers are produced daily and sometimes relying on antivirus alone is not enough. Unlike viruses and trojans, keyloggers are not heavy on system resources and you will not feel slow down on your computer if you have one which makes them harder to sport with regular work. Some of them can be even tracking you on the website and not even be physically present on your computer. Generally, we could categorize keylogger into 4 categories:

1. Web browser-based keylogger. Some websites would have CSS scripts, input web forms, or so-called man in the middle keylogger. Lucky for us even Windows defenders with the latest update can detect this type of keylogger and successfully deal with it and how keylogger itself is not present on our system we are safe.
2. General spyware keylogger. This keylogger is present in your system, usually, it infected it via email attachment, social media download, torrent download, some malicious so-called fixer application, etc. Most antivirus applications and windows defenders can detect these types as well and remove them successfully.
3. Kernel-level keylogger. This keylogger is a more dangerous type they tend to operate underneath Windows as a rootkit and can go undetected by antivirus and windows defenders.
4. Hypervisor-based keylogger. This is the most dangerous keylogger, they use virtualization techniques to hide and mask themselves as a replica of the operating system and they scan all keystrokes by the user. These are very rare keyloggers but they do exist.

If you suspect that you have a keylogger or just want to check your system for precaution reasons follow these tips and guides and luckily you will solve your issue in no time and your data will be safe.

1. Use Task Manager to find suspicious entries.

   Task manager is a great application implemented in Windows that is constantly monitoring and showing all services, applications, and processes currently running on your system and thus a great tool to monitor your system if you know how to use it. First, open task manager by pressing CTRL + SHIFT + ESC Then take a good look into it, try to find suspicious names, probably duplicate of running application, something like Windows logon application, or keylog or anything similar which seems out of ordinary. If you manage to find a suspicious running application right-click on it and close it. Also while you are in task manager jump into the startup tab and check to see are there some unusual applications starting with your Windows, if you find anything, disable it right away. This is the most simple and quickest way to get some information right away if you suspect to have some simpler keylogger in your system.

2. Use the command prompt to monitor your network.

   In order to check connections to your computer and find potential suspicious ones start the command prompt in administrator mode, press ⊞ Win + X, and choose command prompt (administrator). type in netstat -b and press ENTER. All website and application connections to your computer are now visible. ignore svchost, edge browser, windows store, etc ad check the IP of the remaining ones using the internet.

3. Use keystroke encryption.

   Install encrypting software and even if you have a keylogger, the application will encrypt each stroke and all that attacker will get is gibberish

Please remember to always download files from trusted sources, do not open unknown emails, and do not share your information publicly. Take common protection steps in order to protect yourself in the digital world.

Windows 11 has brought some new features and changed some of the existing ones. One of these changes includes quick switching of audio devices which will play audio. Audio switching can still be done under the taskbar, it is just a little different and one could say even hidden. Follow this quick guide and you will be switching from your headphones to speakers as an example in a matter of seconds.

1. Click on the speaker icon located in the far-right part of the taskbar.
2. After the quick settings menu appears click on the right arrow located right of the volume slider. If the arrow is not present, instead of click on the pencil icon, then on add, and finally select Volume from the list.
3. After clicking on the arrow icon, a list of all enabled audio devices on the system will replace the volume slider. Click on the desired audio device in order to make it active.
4. Click anywhere outside the quick setting menu to save changes and close it.

Note: in the Quick settings menu if you choose More Volume Settings it will bring you to System > Sound where you can access more sound input and output options.

Athwbx.sys or the Qualcomm Atheros driver file is known to trigger several Blue Screen of Death errors. This occurs when the driver gets corrupted or when the operating system is unable to access or find it. In addition, bad sectors in the hard disk or RAM can also cause BSOD errors. The athwbx.sys file is known to cause the following BSOD errors listed below:

• SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (athwbx.sys)
• STOP 0x0000000A: IRQL_NOT_LESS_EQUAL (athwbx.sys)
• STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED (athwbx.sys)
• STOP 0×00000050: PAGE_FAULT_IN_NONPAGED_AREA (athwbx.sys)
• Your PC ran into a problem and needs to restart. You can search online later for this error: athwbx.sys

Before you proceed with the troubleshooting tips given below, you might want to try performing System Restore as it could resolve Blue Screen errors caused by the athwbx.sys file. To run System Restore, follow these steps:

• 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 check if the problem is fixed or not.

If System Restore didn’t help in fixing the Blue Screen error, now’s the time for you to resort to the troubleshooting tips provided below but before you get started, make sure that you create a System Restore point first.

Option 1 – Try recreating the athwbx.sys file

The first thing you can try is to recreate the athwbx.sys file. Every time your Windows 10 PC boots up, it looks for all the system drivers in place and if it is unable to find them, it tries to create them. This is why if you remove your corrupt driver file, chances are, you might get a fixed file recreated just for you. How? Refer to the steps below.

• Boot your Windows 10 PC in Safe Mode.
• Then open File Explorer and navigate to this location: C:/Windows/System32/drivers
• From there, look for the file named sys and rename it to athwbx.old.

Note: As you can see, the file’s extension has changed from .sys to .old.

• Now restart your computer and check if the athwbx.sys Blue Screen error is now fixed.

Option 2 – Try to update or rollback your device drivers

If the first option didn’t work for you, then it’s time to either update or roll back the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers and right-click on them to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 3 – Run the System File Checker Scan

System File Checker or 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

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.

• Restart your computer.

Option 4 – Try to run the CHKDSK utility

Running the CHKDSK utility might also help you resolve the athwbx.sys Blue Screen error. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the following command and hit Enter:

chkdsk /f /r

• Wait for the process to be completed and then restart your computer.

Option 5 – Run the Memory Diagnostic Tool

Running the Windows Memory Diagnostic tool in Windows 10 might also help you in fixing the athwbx.sys Blue Screen error. Refer to the steps below on how to run this tool:

• Tap the Win + R keys to open Run and type exe and hit Enter to open the Windows Memory Diagnostic Tool.
• After that, it will give two options such as:
  • Restart now and check for problems (Recommended)
  • Check for problems the next time I start my computer
• Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Note: After you select the option, your PC will restart and check for memory-based issues. If it finds any issues, it will automatically fix them and if there’s no issue found, then it’s most likely not a memory-based issue so you should try the other options given below.

Option 6 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like athwbx.sys. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

There is a lot of software on the market today, but from time to time we discover something extraordinary and unique worth sharing and today we have a threat for you. Ventoy is a tool that will help you with system reinstallations and system maintenance once and for all.

If you are a computer user that has multiple operating systems or you are installing and maintaining different hardware via different OS there is a high chance that you have multiple USB sticks with different operating systems on them.

Now the problem with that is that there are probably too many unlabeled sticks around or you do not have enough so you keep making system USBs depending on which one you might need.

Ventoy solves all of these problems by letting you have as many operating systems images as your USB has capacity. The only thing you need to do is get the software here: https://www.ventoy.net/en/index.html and make a USB with it, then you can freely just copy your ISO images onto the USB and once it is inserted into the computer you will be given a menu to choose which one you would like to start with, simple as that.

Features

• 100% open source (license)
• Very simple to use (Get started)
• Fast (limited only by the speed of copying the iso file)
• Can be installed in USB/Local Disk/SSD/NVMe/SD Card
• Directly boot from ISO/WIM/IMG/VHD(x)/EFI files, no extraction needed
• Support to browse and boot ISO/WIM/IMG/VHD(x)/EFI files in local disk Notes
• No need to be continuous in disk for ISO/WIM/IMG/VHD(x)/EFI files
• Both MBR and GPT partition styles are supported
• x86 Legacy BIOS, IA32 UEFI, x86_64 UEFI, ARM64 UEFI, MIPS64EL UEFI supported
• IA32/x86_64 UEFI Secure Boot supported Notes
• Linux Persistence supported Notes
• Windows auto installation supported Notes
• Linux auto installation supported Notes
• Variables Expansion supported for Windows/Linux auto-installation script Notes
• FAT32/exFAT/NTFS/UDF/XFS/Ext2(3)(4) supported for main partition
• ISO files larger than 4GB supported

• Menu alias, Menu tip message supported
• Password protect supported
• Native boot menu style for Legacy & UEFI
• Most types of OS supported, 1000+ iso files tested
• Linux vDisk(vhd/vdi/raw...) boot solution Notes
• Not only boot but also complete the installation process
• Menu dynamically switchable between ListView and TreeView mode Notes
• "Ventoy Compatible" concept
• Plugin Framework and GUI plugin configurator
• Injection of files into runtime environment
• Boot configuration file dynamically replacement
• Highly customizable theme and menu style
• USB drive write-protected support
• USB normal use unaffected
• Data nondestructive during a version upgrade
• No need to update Ventoy when a new distro is released

‘R6025 pure virtual function call’ is a runtime error that occurs suddenly on the screen and disrupts the program being run prior to it. This error display indicates that the program has been corrupted. R6025 runtime error usually occurs with the Visual C++ framework.

Solution

Error Causes

This error occurs when the C++ program crashes which is usually because of the malfunctioning or missing of the device driver or incomplete device driver files. It happens because your application indirectly calls a pure virtual member function in a context where a call to the function is invalid. Most of the time, the compiler detects it and reports it as an error when building the application. R6025 error is usually detected at run time.

Further Information and Manual Repair

To fix the R6025 pure virtual function call error, you need to find the call to the pure virtual function. After you find the call, you need to rewrite the code so that it is not called again. There are 2 ways to do this:

Alternative 1

One way to fix the R6025 pure virtual function call is to replace the function with an implementation that calls the Windows API function DebugBreak. The DebugBreak causes a hard-coded breakpoint. Once the code stops running at this breakpoint, it is easy for you to view the call stack. By viewing the call stack you can identify the place where the function was actually called.

Alternative 2

Another quick way to find a call to a pure virtual function to fix the R6025 error is to set a breakpoint on the _purecall function that is usually found in PureVirt.c. By breaking this function you can trace the problem occurring and rewrite the call to ensure the error does not occur and the program you are trying to develop on the Visual C++ framework is easily developed. If R6025 Error is related to Windows Registry Problem Then here’s how you can fix the problem: To fix the runtime error R6025, run registry cleaner software to scan and fix all errors.  This alternative is suitable if the R6025 error is related to the Windows registry problem and where the error has occurred due to corrupted or malicious registry entries. You can download the registry cleaner repair tool for free. Run it to scan errors and then click the fix error button to repair the problem immediately.

Installer Error 1603 - What is it?

Installer Error 1603 message occurs during the installation of the Microsoft Windows installer Package. The error message is often displayed as the following:

'Error 1603: A fatal error occurred during installation.'

It indicates a problem occurred during the installation process and unsuccessful installation.

Solution

Error Causes

The installer error 1603 may occur if:

• The folder you are trying to install the Windows Installer package to is encrypted
• The system account does not have full control permissions
• Incorrect installation
• Registry issues

Further Information and Manual Repair

To resolve this error on your system, try the solutions listed below:

Solution 1: Install-Package in an Un-Encrypted Folder

Try installing the package to a folder that is not encrypted. However, if the error still persists, try other solutions listed below.

Solution 2: Enable Full System Control Permissions

Sometimes the error may occur when you don’t have system full control permissions. To enjoy full control permissions here’s what you need to do, go to my computer and right-click the drive that you wish to install the Windows Installer Package to. After that click properties and the security tab. If you can’t locate the security tab, this means your Simple File Sharing feature is turned on. You need to turn it off to continue. For that go to my computer, tools, and then click folder options. Now here press the view tab and check the Simple File Sharing box to turn it off. Press OK to save changes. Now you will be able to locate the security tab. Click on the Security tab and verify the name box that contains the system user account. If the system user account is empty then insert the account name. To insert, click Add, and then select user's dialog box, add a name, and close. Now go to the permissions section and check the box ‘Allow’ under full control. After that go to the ‘Advanced’ tab and do the following: If you are an XP user, select ‘Replace permission entries on all child objects with entries shown here that apply to child objects’ and then press OK to confirm. If you are not an XP user, then follow the same instructions but select the check box that says ‘Reset permissions on all child objects and enable propagation of inheritable permissions’ for the system account. Now click OK to confirm. To activate changes you will have to wait for a while. Once the changes are activated, try installing the Windows Installer package again.

Solution 3: Clean and Repair Registry

The Installer error 1630 can occur due to registry problems as well. To resolve registry-related issues download Restoro. This is a cutting-edge and advanced registry cleaner that scans your entire PC for registry-related errors in seconds and resolves them spontaneously. It removes all the unnecessary junk files, bad keys, invalid registry entries, cookies, and internet history cluttering and corrupting the registry. It repairs the damaged system files and repairs the registry right away thereby resolving Installer Error 1630 on your PC. It is safe and efficient. It is embedded with an intuitive algorithm and a sophisticated user-friendly interface. It is easy to use and operate. You can download it on any Windows version. Besides functioning as a registry cleaner, it also functions as an antivirus and a system optimizer. Click here to download Restoro on your PC to resolve all registry issues generating the installer error 1603 on your system.