Creating custom Keyboard shortcuts in Windows

As you know, the internet has changed the world immensely. Nowadays, JavaScript is pushing the modern web ahead. One of the things that make these experiences with the internet seamless and with less clutter is redirection. It is often used on web pages and there are times when a user is prompted about them and most of the time, we barely notice them. However, there are also instances when things can go wrong with redirects as they could become a loop that could mess things up. And since the browser takes a lot of system resources, redirection can result in a poor user experience. That’s why in this post, you will be guided on how you can stop these automatic redirects on browsers such as Microsoft Edge, Google Chrome, and Mozilla Firefox, on your Windows 10 computer. To get started, refer to each one of the options provided below to stop automatic redirects in Microsoft Edge, Google Chrome, and Mozilla Firefox.

Option 1 – Configure the browsers to stop pop-ups and deceptive contents

There are a lot of browsers with built-in settings that allow users to stop pop-ups and deceptive content. To configure these settings, refer to these steps:

• Microsoft Edge:

  • Click on the three horizontal dots icon or the menu button.
  • Next, click on Settings and select Privacy & Security from the left side navigation.
  • After that, scroll down on the right-side panel and look for Block pop-ups and Windows Defender SmartScreen and then turn their toggle buttons to On.

• Google Chrome:

  • Open Google Chrome and click on the three vertical dots icon for the menu located in the top right corner of the browser.
  • Next, click on Settings and scroll down until you see the Advanced option. Click on it to open the Advanced Settings.
  • Now scroll down until you reach the Privacy and Security section and look for the Safe browsing option and turn its toggle button to On.

• Mozilla Firefox

  • Open Mozilla and click on the three horizontal lines icon for the menu button located in the top right corner of the browser and click on Options.
  • Next, go to the Settings section and click the Privacy & Security tab and scroll down and then click on Permissions.
  • From there, make sure that the Block pop-up windows checkbox is checked.
  • Finally, scroll down until you reach the Security section and make sure that the checkbox for the Block dangerous and deceptive content is checked.

Option 2 – Try to reset Winsock, TCP/IP & Flush DNS

To stop redirects, you can also reset Winsock and the TCP/IP as well as flush the DNS cache. To do so, follow these steps:

• Right-click on the Start button and click on Command Prompt (administrator) so you can pull up an elevated Command Prompt.
• After that, execute each one of the commands listed below. And after you typed in one after the other, you have to hit Enter.

1. netsh winsock reset – type in this command to reset Winsock
2. netsh int ip reset resettcpip.txt – type in this command to reset TCP/IP
3. ipconfig /flushdns – type in this command to flush the DNS cache

• Next, restart your PC and check if the problem’s fixed.

Option 3 – Edit your Hosts File

• Tap the Win + R keys to open then type in %WinDir% and then click OK.
• Go to System32/drivers/etc.
• Open the host file using Notepad.
• Delete all the suspicious entries.
• After that, save the changes you’ve made and close the file.

Error Code 7 - What is it?

This is a typical system error that occurs during Windows setup. To be precise, this error may pop on your computer screen during the text mode portion of Windows setup. The setup hangs and stops responding and the error message is displayed in either one of the following formats:

‘The file I386Ntkrnlmp.exe could not be loaded. The error code is 7.’ or ‘The file I386L_intl.nlf could not be loaded. The error code is 7.’

Solution

Error Causes

Error 7 may be triggered due to several reasons but the 2 most common causes for this error code are:

• Incorrect settings of the BIOS
• Faulty RAM modules
• Registry corruption

Further Information and Manual Repair

To resolve this error on your system, here are some easy and effective DIY methods that you can try.

Method 1 - Change Back the BIOS to its Default Settings

If the underlying cause of error code 7 is related to incorrect BIOS settings, then it is recommended to restore default settings to resolve. You can reset your computer’s BIOS (basic input and output system) settings to factory defaults by selecting the restore defaults option within BIOS or by removing CMOS ( Complementary Metal Oxide Semi-Conductor) battery from your unplugged computer for about five minutes. The battery removal method requires opening the computer case, so only attempt it if you are unable to access BIOS. To reset BIOS follow these steps, reboot your PC and then press the key assigned to loading BIOS during your computer boot splash screen. The key assigned to load and access BIOS varies from manufacturer to manufacturer but usually, it's F1, F2, or F12. Once you enter the BIOS, select the ‘Restore Defaults’ option listed in the menu.  I t may be a keyboard shortcut or be under the Advanced settings menu. Confirm settings and then exit BIOS. Hopefully, this will resolve Error 7.

Method 2 - Remove the Faulty RAM

When error code 7 is triggered by faulty RAM modules, then to resolve it simply remove the memory modules that are installed in the computer. If the error code is displayed again after you remove the memory module, remove a different memory module. This procedure requires you to reboot your PC several times to identify the specific memory module that is not working properly.

Method 3 - Repair the Corrupted Registry

Error code 7 is sometimes also linked with registry issues. If the reason for the error occurrence is a damaged or corrupted registry, then simply download Restoro. This is a powerful PC Fixer embedded with a registry cleaner. It is easy to operate and user-friendly. The registry cleaner detects and removes all errors in seconds. It cleans the registry and repairs the damages in no time. Click here to download Restoro.

Windows users need to be on high alert. Microsoft has confirmed a critical vulnerability has been found in all versions of Windows which presents an immediate threat, and you need to act now. A critical new zero-day hack has been found which affects all Windows versions. Tracked as CVE-2021-34484, the “zero-day” flaw enables hackers to breach all versions of Windows (including Windows 10, Windows 11, and Windows Server 2022) and take control of your computer. Microsoft mistakenly thought it had patched the vulnerability (which was first found in August) when it was publicly disclosed in October. But the fix itself was found to be flawed, something the company admitted, and this drew even more attention to the vulnerability. Microsoft subsequently promised to “take appropriate action to keep customers protected” but two weeks later, a new fix has still not arrived. Luckily the third-party security specialist 0patch has beaten Microsoft to the punch with a ‘micropatch that it has now made available for all Windows users “Micropatches for this vulnerability will be free until Microsoft has issued an official fix," 0patch confirmed. You will need to register for a 0patch account and install its download agent before the fix can be applied, but with 0patch fast becoming a go-to destination for hot fixes which beat software companies to the punch this is a no brainer. Hopes will be high that Microsoft can release an effective patch sooner rather than later but, until then, all Windows users must act now if they want to be safe. Download 0patch here: https://blog.0patch.com/2021/11/micropatching-incompletely-patched.html

QuickLook app is one of the best options to preview files without opening them in Windows 10. It works similar to the Quick Look feature of macOS. This Microsoft Store app has some really interesting features. It lets you preview images, documents, and media files. Also, just a hotkey is needed to preview the content of a file. There is no interface for the app. Only a preview window is visible. You can also expand the preview window to full size. Apart from that, it lets you keep the preview window on top of the other opened applications. For image files, it also provides the EXIF data. After installing this app, just select some file that you want to preview, and press the Spacebar key. That’s it! The preview window will open immediately to view the file content. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

We have talked about gaming on old computers and have covered new and upcoming Steam deck handheld console. Today we are combining old gaming with a handheld console and our target of talk is Retroid pocket 2. This product is packed with really high-quality plastic and with some great features in it. So let's dive into this cool handheld in more detail and find out why we like it so much.

Good manufacturing quality

Plastic and overall manufacturing quality are really, really good. The battery is great, packing 4000mAh that can hold over 3 hours of nonstop gaming, and all buttons and joysticks are great. The screen is a 640 x 480 60Hz 3.5″ IPS screen (4:3 aspect ratio) that performs really great for its purpose, retro gaming. There is a Digital D-Pad and dual analog joysticks. The right joystick is the lower profile to avoid being accidentally moved when pressing the four gaming buttons. There are three buttons at the bottom which are Home, Start, and Select. On either side are good-quality stereo speakers. On the bottom of the device are a Micro SD Card slot and a 3.5mm headphone port. On the top of the device are Left and Right shoulder and trigger buttons. There are the power button and volume adjustments. There are a USB Type-C OTG port and a Micro HDMI output for connection to a TV.

Good technical statistics

Good, not great but then again since this is retro handheld you cannot really expect some crazy stuff like alder lake inside. So the console is punching ARM Cortex A7 CPU with 2 cores and a clock of 1.5GHz paired with ARM Mali 400-MP2 500MHz GPU. The console has 1GB LPDDR3 RAM memory and 8GB eMMC Storage where 5GB is freely available, the rest is taken for OS. As mentioned before the display is 640x480 resolution with a size of 3.5″. The battery is Lithium-Ion with a power of 4000mAh and on the handheld, there is a USB Type-C connector, 3.5mm headphone jack, and Micro-HDMI. It also has Wifi/Bluetooth 4.0

Retroid Pocket 2 OS and support

Pocket 2 comes with Android 6 but you can update its firmware to the 8.1 version on the official site that I would highly recommend. New versions of the handheld will come with 8.1 on it from the box. Having Android as OS opens many possibilities like you can download Android apps such as Steam Link, allowing you to play actual PC games on your Retroid Pocket 2. Not just that, if it does get a newer version of Android it could even have the ability to use xCloud, Xbox’s cloud gaming service. Of course, hardware will not be able to handle modern games but the option is still there and for some old PC titles available on steam like Commander Keen, for example, this is a great option. The console can emulate basically everything up to Dreamcast, including N64, PSP, and Playstation 1. It can emulate Nintendo DS also, but it can only do so with one screen. The only problem with this console is you will need to install and update Apps. You’ll need to learn about RetroArch, an app that lets you download emulators or cores to play games.

Retroid price

The last thing on the list is the price of the console itself. Going just under the 100$ mark this really makes it an affordable option for plenty of people that would like to experience retro handheld gaming or for ones like me, nostalgic gamers wanting to relive some era of playing games on the road.

Conclusion

Among Chinese handheld devices for retro gaming, Retroid Pocket 2 is really on top of what the market can offer. If you are looking for a great handheld retro console and are not afraid of little dive-ins into the OS and various configurations, Pocket 2 will reward you with plenty and wide emulation support.

Coming in October for insiders and in November for all in the update, Microsoft has prepared a series of updates which they call an "additional set of experiences"

These updates are looked upon by Panos Panay, a vice executive president at Microsoft & chief product officer for Windows and devices as sort of makeup tests. They will consist of new additions with the biggest one being a tabbed version of File Explorer.

File Explorer received a UI makeover in the last update but the tabbed interface was missing which was expected by many users so it will come in following the next update.

The rest of the features that we will receive are an updated Photos application, Suggested Actions in the Windows Shell, Overflow menu for the taskbar, and improved Nearby Share.

The tabbed File Explorer interface is essentially File Explorer’s version of Sets, the tabbed window interface that Microsoft tested out several years ago. In testing, the tabbed interface proved handy for moving and copying files, and we’d expect the same once the feature formally goes live. The difference between Sets and the tabbed File Explorer interface is Sets allowed for multiple applications to be clustered together via tabs.

Photos app will include a “new photos-managing experience that brings a gorgeous gallery, simplifying browsing, finding, management and consumption of your collection of photos.” It will allow “easy backup to OneDrive” and a “delightful Memories experience.”

As for other features, nothing specifically was said except giving just some tips on what will they bring, it is obvious that File Explorer and the photos app were the main focus for MS in this upcoming update.

Code 42 - What is it?

Code 42 Error is referred to as a Device Manager Error code. Before we explain what this code indicates, it is important to understand what ‘Device Manager’ is and its functions.

Device Manager is basically a Windows tool that helps manage devices attached to the system such as the Printer, Scanner and the USB Device. The Device Manager Error code 42 occurs when a duplicate device is detected.

Error Code 42 is displayed in the following format:

“Windows cannot load the device driver for this hardware because there is a duplicate device already running in the system. Code 42”

Solution

Error Causes

Narrowing down to one particular cause for error code 42 is not virtually possible because it may be triggered due to many underlying reasons. These include:

• When a bus driver incorrectly generates and creates 2 identically named devices
• When a device with a serial number is found in a new location without being removed from its original location
• Mis-configured drivers

No matter what the reason for this error code,, to avoid inconvenience and to ensure proper hardware performance, it is advisable to fix it right away without any delay.

Further Information and Manual Repair

If you’re not technically sound, the code 42 message display can panic you. But don’t worry, the error message sounds complex but it is quite easy to fix.

To resolve code 42 in a few minutes, simply try the methods given below. These methods are easy-to-perform, effective and more importantly require no technical expertise.

Method 1 - Restart Your System

Code 42 can pop up due to some temporary glitch in the Device Manager. By simply restarting your PC, you can resolve this problem.

Therefore, first things first, restart your system. However, in case it doesn’t work out, try other methods.

Method 2 - Launch the Troubleshooting Wizard

Launch the troubleshooting wizard to find the underlying problem and resolve it accordingly. To do this, proceed with the following steps:

• Go to the start menu
• Type Device Manager in the search bar and press enter
• Now click on the ‘General Tab’
• Then click on ‘Trouble Shoot’ to launch the Troubleshooting Wizard
• After that follow the instructions in this Wizard to diagnose the problem and resolve it.

Method 3 - Restore Your PC to its Previous State

Another method to fix code 42 is to use the System Restore tool to restore your PC to its previous working state before the error popped up. To do this,

• Go to the start menu
• Type System Restore in the search bar and press enter
• Now click on ‘Restore my computer to an earlier time’ and then click ‘Next’
• After that select the restore point on the restore point list and confirm settings
• Restart your PC to activate changes
• Before restoring your PC to its previous state, create a backup. By creating data backup you can avoid data loss issues, which are likely to occur during this process.

Creating backup manually can be time-consuming and a painstaking task. The best way to create backup and restore your PC to its normal state is to download DriverFIX.

It is a user-friendly device driver management software that helps create data backup automatically and simultaneously restores your PC back to its normal working state in a few seconds.

This software is compatible with all Windows versions.

Click here to download DriverFIX on your system to resolve error code 42.

Skinning of applications is not new to PC users, but did you knew you could skin Steam? With skin, you can customize the UI and style of the client to what you want making it more personal and to your liking. First thing is to find the skin that you would like to install. There are a lot of sites where you could find custom made Steam skins but we would recommend steamskins.org The site itself is organized in tabs with different sections, once you click on the tab you will get a list of skins available for chosen section. If you click on the skin you will be taken to skin page detail where you can find what skin is aiming for, its legibility, a record of how the skin has been altered over time, or some mix of these aspects. Note that some skins might have issues like some buttons might be missing from big picture mode but so far none of the skins has any kind of client breaking feature, only functionality one.

Downloading skin

Once you have chosen desired skin and while on the skin details page, scroll to the middle of the page just above the Related Skins sections with two options: Direct Download and External Download. Now usually I would recommend Direct download but in this case, I would advise going with External Download for the simple reason that the External link will send you to the developer's website where there is a higher chance to get the latest updated skin.

Installing it in Steam

Once the skin is downloaded you will first need to create a skin folder inside your Steam installation location. Navigate to your Steam installation folder (default: C:\Program Files (x86)\Steam) and create a new folder inside it. Give new folder name Skins and confirm. Extract the skin zip file in the newly made folder. Once the file is extracted you can delete the ZIP file if you wish. Go to your Steam client and go to Steam>Settings. In settings select Interface on the left bar and on the right part then click the Select the skin you wish Steam to use the drop-down menu and select the skin that you wish to use. Confirm and restart your Steam client

Reverting to old skin

If you found skin unappealing or, unfortunately, has some functions missing you can always choose another skin or revert back to default Steam skin. Default Steam skin is named in the drop-down menu as < default skin >.

The ntkrnlmp.exe file is a file associated with the Windows operating system’s NT Kernel and other system processes. It is also related to the “CRITICAL PROCESS DIED” error. So if you encounter a Blue Screen of Death error that’s related to this file, then you’ve come to the right place as this post will guide you in fixing the ntkrnlmp.exe Blue Screen error. This kind of Blue Screen error might be caused by the file getting corrupted or infected with some malware. Aside from these causes, the error might also be due to the corruption and malfunction of the graphics card drivers. Before you troubleshoot the problem, you might want to try performing System Restore especially if you tend to create a System Restore point every now and then. Performing System Restore could help you resolve the ntkrnlmp.exe Stop error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

• 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, then proceed to the given options below.

Option 1 – Disable the C-states and EIST in the BIOS

The first thing you can do is try to disable the C-states and EIST in the BIOS. To do that, refer to the steps given below.

• Go to the BIOS and from there look for an option named CPU Configuration which can usually be found under the Advanced menu.
• Next, look for CPU Power Management and under that section, disable both the “Intel EIST” and “Intel C-state” options.
• After you disable them, save the changes you’ve made and exit the BIOS.
• Now restart your computer and check if the ntkrnlmp.exe BSOD error is now fixed.

Option 2 – Try to update, rollback or disable drivers

If the first option didn’t help in fixing the ntkrnlmp.exe Blue Screen error the next thing you can do is to roll back, or update, or disable device drivers in your computer. 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 – Configure the Driver Verifier Manager

The Driver Verifier Manager is another tool in Windows that could help you fix driver-related issues. And so if you want to fix the ntkrnlmp.exe Blue Screen error you need to use the Driver Verifier Manager:

• Type in the keyword “Verifier” in the Cortana search box to search for Verifier in Windows 10.
• After that, select the option “Create custom settings”.
• Make sure that you have checked everything except the options “DDI compliance checking” and “Randomized low resources simulation”.
• Next, select the option “Select driver names from a list” option.
• Afterward, you have to select all the drivers from any unofficial or third-party provider. To simply put it, you have to select all the drivers that are not supplied by Microsoft.
• Then click on the Finish button.
• Open Command Prompt as administrator and execute this command – verifier /querysettings
• The command you just executed will display the Driver Verifier settings so if you see any of the flags enabled boot your Windows 10 PC into Safe Mode.
• Open the Command Prompt as admin again and run this command – verifier /reset
• The command will reset the Driver Verifier. Once the process is done, restart your PC and check.

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

If the Diagnostic Data level in your Windows 10 computer is configured manually to the non-default security setting of zero and you’ve encountered an error code of 0xc0000005, read on as this post will guide you in fixing the problem with the Remote Access Connection Manager Service. In relation to error 0xc0000005, you might also encounter an error in the Application section of Windows Logs in the Event Viewer, along with the Event ID 1000 which would most likely have a reference of “svchost.exe_RasMan” and “rasman.dll”. Before you troubleshoot the problem, keep in mind that the Remote Access Connection Manager or RasMan service is the one that manages dial-up and VPN connections from the computer to the internet as well as other remote networks. Each time you connect, the Services dials the connection or sends out a request for a VPN connection. However, the error 0xc0000005, only occurs when a VPN profile is configured as “Always On VPN or “AOVPN” connection with or without a device tunnel. There are several options you can check out to resolve this error, you can try to install the KB Update 4505903 or fix it via Group Policy. You could also try to enable Telemetry from the Settings app or enable it via Registry Editor. For more information, make sure to check out the provided options below.

Option 1 – Try installing the KB Update 4505903

The first thing you can do to fix the problem is to make sure that you’ve already installed the KB Update 4505903 in your computer. If not, then you have to go to Settings > Update & Security > Windows Update and from there select the Check for updates link. You need to get the standalone package if you are using the Microsoft Update Catalog to update your computer and for that, you have to the website of the Microsoft Update Catalog. On the other hand, if you are using the Windows Server Update Services or WSUS, then you can just manually import the KB Update 4505903 into WSUS.

Option 2 – Try to enable Telemetry in the Group Policy and run the RASMAN service

The next thing you can do to fix the problem is to enable Telemetry via Group Policy and then run the RASMAN service. To do that, follow these steps:

• Tap the Win + R keys to open the Run dialog box and type “gpedit.msc” in the field and hit Enter to open the Group Policy Editor.
• Next, navigate to Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds > Allow Telemetry.
• After that, open the policy and select one of the security levels like Basic, Enhanced, and Full.
• Then click on the Apply and OK buttons to save the changes made and close the Group Policy Editor.
• Once one, open the Run dialog box again and type “services.msc” in the field, and hit Enter to open the Windows Services Manager.
• From there, look for the Remote Access Connection Manager Service and restart it. And then check if it resolved the problem or not...

Option 3 – Try enabling Telemetry via Settings

• Tap the Win + I keys to open the Settings app.
• Next, go to Privacy > Diagnostics and Feedback and select Basic or Enhanced under the Diagnostic data.
• After that, tap the Win + R keys to launch Run and type “services.msc” in the field, and hit Enter to open the Services Manager.
• From there, look for the Remote Access Connection Manager Service and restart it.

Option 4 – Try to enable Telemetry via Registry Editor

• Launch the Run utility and type “regedit” in the field and tap Enter to open the Registry Editor.
• Then navigate to this path: HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsDataCollection
• From this path, look for “AllowTelemetry” and double click on it.
• Now enter the values, 1, 2, 3 for Basic, Enhanced, Full, respectively.
• If you can’t find AllowTelemetry, then just create a DWORD (32-bit) and name it “AllowTelemetry” and edit its value.
• Once done, exit the Registry Editor and restart the Remote Access Connection Manager Service from the Services Manager.