Tips and tricks for longer SSD life

Microsoft just released Windows 11 Insider build 22000.71. Let’s dive in and see what it brings with you.

Changes and features

New entertainment widget. The entertainment widget allows you to see new and featured movie titles available in the Microsoft Store. Selecting a movie will direct you to the Microsoft Store to see more information about that title. Just open widgets and click or tap on the “Add widgets” button and choose the entertainment widget. For now, the entertainment widget is available for Insiders in the following countries: US, UK, CA, DE, FR, AU, JP. The new context menus and other right-click menus have been updated to use acrylic material. We are testing the usability of a SplitButton for making new folders and files in the File Explorer command bar. The Taskbar previews (when you mouse-over open apps on the Taskbar) have been updated to reflect the new visual design of Windows 11.

Fixes

Taskbar:

• We fixed an issue where if you drag app icons on the Taskbar to rearrange them, it was making the apps launch or minimize when you released the icon.
• Using a long press with a touch on an app icon in the Taskbar to open the jump list should now work.
• After right-clicking the Start icon in the Taskbar, clicking somewhere else should now dismiss the menu more reliably.
• Shift + Right-click on an app icon in the Taskbar will now bring up the window menu like it used to and not the jump list.
• We’ve addressed an issue that was making your mouse move slowly when hovering over the Taskbar previews.
• We’ve included the fix for an issue when using multiple Desktops where an app icon in the taskbar might give the appearance of multiple windows being open when that wasn’t the case on that Desktop.
• When using the Amharic IME you should no longer see an unexpected X next to the IME icon in the taskbar.
• The issue where if you click on the input indicator on the Taskbar and it would unexpectedly highlight Quick Settings has been fixed.
• When you hover over Task View, the preview flyout for your Desktops will no longer pop back up after using Esc to dismiss them.
• We made a fix to address an issue where explorer.exe might crash after hovering over the Task View icon in the Taskbar.
• We fixed an issue where the selected date in the calendar flyout was out of sync with the date in the Taskbar.
• We made an update to address a scenario resulting in some Insiders not seeing the lunar calendar text in the calendar flyout when enabled in Settings.
• This flight addressed an issue that could unexpectedly make the Taskbar background transparent.
• Right-clicking the focus assist icon in the taskbar should now show a context menu.
• The issue from the previous flight where icons in the taskbar corner were getting crushed against the top of the Taskbar has been addressed.
• The tooltip for the location in use icon in the Taskbar should no longer appear blank sometimes.

Settings:

• We fixed an issue making Settings crash on launch periodically.
• Using the volume mixer sliders in Sound Settings should be more responsive now, as well as the page responsiveness as a whole.
• We fixed an issue resulting in Disk and Volumes Settings’ change size option being clipped.
• There was a non-functional verify link under Backup Settings – this has been fixed.
• The Power and Battery Settings page should no longer be reporting that the battery saver is engaged if it’s not.
• The Power and Battery Settings page should also now not crash when launched from Quick Settings.
• We fixed a grammatical error in the Sign-in Settings text.
• The “I forgot my PIN” link was unexpectedly missing in Sign-in Settings when a PIN was set up and has now been returned.
• The issue where the Move option under Apps & Features in Settings wasn’t working reliably should be addressed in this build.
• We’ve mitigated a problem where some of the colors in Settings weren’t updating after switching between dark and light mode, leaving the unreadable text.
• We’ve done some work to help improve the performance of Settings when switching between light and dark mode.
• We addressed an issue where some of the elements of the Themes page in Settings would end up crowded together when the window size was small.
• We resolved an issue where the Pen menu toggle under Taskbar Settings was not in sync with the actual state of the feature.
• Changes made to “Dismiss notification after this amount of time” in Accessibility Settings should now persist.
• Some of the icons you could enable in Taskbar Settings were erroneously labeled Windows Explorer even though that’s not what they were – this should now be fixed.
• The Connect text in Quick Settings has been updated to say Cast.

File Explorer:

• Clicking the command bar button twice should now close any dropdown that appeared.
• The new command bar should now appear when “Open folders in a separate process” is enabled under File Explorer Options > View.
• This build addresses an issue where right-clicking a file and selecting Open With > Choose another app might launch the file in the default app rather than opening the Open With dialog.
• Fixed an issue the desktop and File Explorer context menu would stop launching.

Search:

• We fixed an issue where the option to verify your account in Search wasn’t working.
• Hovering over the Search icon on a secondary monitor will now show the flyout on the correct monitor.
• Search should now work if you open Start and start typing after having gone to the apps list and back.

Widgets:

• When using the Outlook client with a Microsoft account, Calendar, and To-Do updates should sync faster down to the widgets.
• We addressed an issue where if you added multiple widgets quickly from the widget's settings, it could result in some of the widgets not being visible on the board.
• We fixed a bug where widgets could all become stuck in a loading state (blank squares in the window).
• The traffic widget should now follow the Windows mode (light or dark).
• The title of the sports widget should no longer mismatch with the content of the widget.

Other:

• This build addresses an issue where ALT + Tab was getting stuck open sometimes after you released the keys and had to be manually dismissed.
• We made a fix for an issue where Narrator's focus wasn’t ending up on the emoji panel after using the keyboard shortcut to open it.
• Magnifier’s lens view has been updated so the lens now has rounded corners.
• We found an issue that was noticeably impacting Start launch reliability for some Insiders, and have addressed it with this flight.
• We’ve updated the “Most Used” text in the Start menu’s app list so it should no longer be getting clipped.
• Using the semantic zoom in Start’s app list should no longer result in the list being pushed down and to the right off the edge of the window.
• We fixed an issue where if you pressed ⊞ WIN + Z you would need to press Tab before you could use the arrow key to navigate through the snap layouts.
• We addressed an issue where an acrylic area could get left on the screen after repeatedly snapping and unsnapping a window with touch.
• We’ve done some work to mitigate an unexpected flash when moving a snapped window with touch.
• We made a change to help window borders have a little more contrast when “Show accent color on title bars and windows borders” was turned off.

Known issues in Windows 11 repaired

Start:

• In some cases, you might be unable to enter text when using Search from Start or the Taskbar. If you experience the issue, press ⊞ WIN + R on the keyboard to launch the Run dialog box, then close it.
• Based on feedback, we are working on adding access keys to ⊞ WIN + X so that you can do things like “⊞ WIN + X M” to launch Device Manager. Insiders may see this functionality in this build, however, we are currently investigating an issue in which sometimes the option is unexpectedly unavailable.

Taskbar:

• There is an issue in this build where Explorer.exe will crash when the date and time button on the Taskbar is clicked to access new notifications with Focus Assist turned off. The workaround for this is to enable Focus assist to priority or alarms mode. Note that when focus assist is turned on, notification popups won’t appear, but they will be in the notification center when opened.
• The Taskbar will sometimes flicker when switching input methods.
• Taskbar previews may draw partially offscreen.

Settings:

• When launching the Settings app, a brief green flash may appear.
• When using Quick Settings to modify Accessibility settings, the settings UI may not save the selected state.
• The button to rename your PC doesn’t work in this build. If needed, this can be done using sysdm.cpl.
• Settings will crash when clicking “Facial recognition (Windows Hello)” under Sign-in Settings if Windows Hello is already set up.
• Reset this PC and Go back buttons in Settings > System > Recovery does not function. Reset and rollback can be accessed from the Windows Recovery Environment by selecting System > Recovery > Advanced startup, and pressing Restart now. Once in Windows Recovery, choose Troubleshoot.
• Choose Reset this PC to perform a reset.
• Choose Advanced options > Uninstall Updates > Uninstall latest feature update to perform a rollback.

File Explorer:

• exe crashes in a loop for Insiders using the Turkish display language when the battery charge is at 100%.
• When right-clicking the desktop or File Explorer, the resulting context menu and submenus may appear partially off-screen.
• Clicking a desktop icon or context menu entry may result in the wrong item being selected.

Search:

• After clicking the Search icon on the Taskbar, the Search panel may not open. If this occurs, restart the “Windows Explorer” process, and open the search panel again.
• When you hover your mouse over the Search icon on the Taskbar, recent searches may not be displayed. To work around the issue, restart your PC.
• The search panel might appear black and not display any content below the search box.

Widgets:

• Widgets board may appear empty. To work around the issue, you can sign out and then sign back in again.
• Launching links from the widgets board may not invoke apps to the foreground.
• Widgets may be displayed in the wrong size on external monitors. If you encounter this, you can launch the widgets via touch or WIN + W shortcut on your actual PC display first and then launch on your secondary monitors.

Store:

• The install button might not be functional yet in some limited scenarios.
• Rating and reviews are not available for some apps.

Windows Security:

• Device Security is unexpectedly saying “Standard hardware security not supported” for Insiders with supported hardware.
• “Automatic sample submission” is unexpectedly turned off when you restart your PC.

Localization:

• There is an issue where some Insiders may be missing some translations from their user experience for a small subset of languages running the latest Insider Preview builds. To confirm if you have been impacted, please visit this Answers forum post and follow the steps for remediation.

That's is so far, the latest update information on Windows 11 insider build. Stay tuned for more information when it comes as it comes.

A number of users reported lately that their Windows 10 PCs automatically boots into the BIOS whenever they start their computers. And when they tried to exit the BIOS and restart their computers, it still boots into the BIOS. If you are one of the users who experience the same problem, worry not for this post will walk you through what you can do to resolve the problem. Each time a Windows 10 computer boots, it goes through a lot of processes and one of them is where it checks the computer for any hardware issue such as hard drives, peripherals, as well as external devices. So if it finds some issue, the computer will halt the boot process and will boot into the BIOS. To fix this, there are several suggestions you can try. You have to check if you’ve pressed any key, especially the F2 or F12, or Del keys. You also have to check the peripherals and external devices in your computer or update the BIOS or reset it. For more information, make sure to follow each one of the options laid out below.

Option 1 – Try to check for any pressed key

The first thing you can do is to check for any pressed key. This might not make any sense but a pressed key can actually cause this problem. So you have to check if you have the F2 or F12 or Del buttons pressed since these are hardware keys that are usually set by the OEM to boot into the BIOS.

Option 2 – Try checking the physical device connections

You might also want to try checking if there are other devices that are connected to your PC. This is because the configuration of the BIOS or UEFI might be configured in a way that any external device connected to the computer has a higher boot priority compared to the hard disk.  And if it’s really the case, the externally attached disk might be the drive your computer is trying to boot into and not the hard disk. In such cases, Pen Drives, USB storage devices, CDs, DVDs, and so on, are included in this category of physical device connections.

Option 3 – Try to set a proper boot device

If the Boot Manager wasn’t able to locate a proper boot device, then it could be the reason why your computer boots into the BIOS when you turn it on. Thus, you have to check if there is an available proper boot device. You can usually find it under the Boot priority section. However, if you’re unable to locate your hard drive or SSD under the Boot device, then you have to change the hard drive but you have to check first if it is properly plugged in and that it works on other computers. If it works on other PCs, then the problem lies in the motherboard of your computer, and in that case, you have to consult its manufacturer.

Option 4 – Try to update the BIOS

Updating the BIOS can help you fix the issue but as you know, BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “msinfo32” in the field and press Enter to open System Information.
• From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
• After that, you should see the developer and version of the BIOS installed on your PC.
• Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
• If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
• Now double click on the downloaded file and install the new BIOS version on your computer.
• Now restart your computer to apply the changes made.

Note: If updating the BIOS didn’t help, you might want to consider resetting it instead.

Option 5 – Try resetting the BIOS/UEFI configuration

You might also want to reset the BIOS configuration which will lead to arranging the boot configuration since it is intended by the manufacturer. Note that this will get rid of any blockage in the boot process. All you have to do is take out the CMOS battery for a couple of seconds and then put it back again. After that restart, your computer and will be booted directly into Windows. Resetting the BIOS would also get rid of any password set for BIOS and you need to change your CMOS battery in case it didn’t work.

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 you suddenly find your Windows 10 computer stuck on the “Preparing to configure” screen for quite a long time now after you run Windows Update, read on as you will be guided on how you can fix that issue in this post. During an update process, there’s a lot of things that go on in the background which is why Windows Updates take quite a while before it finishes. It can be at 25%, 50%, or even 100% but the only message you’re going to see on your screen is the “Preparing to configure Windows, Don’t turn off your computer”. However, if you notice that the Windows Update is taking a longer time than it’s supposed to, the first option is to wait some more but if it’s still the same, then there’s definitely something wrong. This kind of issue occurs when Windows Update fails to configure in short correctly download and install the update. When this happens, it will revert all the changes which are why you were advised to wait for a couple of hours. There are two possibilities why your computer is stuck on the “Preparing to configure Windows, Don’t turn off your computer” screen. The first one is that the Windows 10 operating system is installing any updates. The second one is when the user profile takes time to load or encounters an error. There are several options you can try to fix the problem. You can try running System Restore or boot your computer in Safe Mode or repair the corrupted profile via Registry Editor. You might also want to try using installation media to boot and repair your computer if the other options didn’t work.

Option 1 – Perform System Restore

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

Note: If you can’t boot into the desktop of your computer, you can run System Restore in the Advanced Startup Options by following these steps:

• Boot your computer into the Advanced Startup Options screen.
• From there, you will see some options to troubleshoot when you can’t log in to Windows in the usual way.
• Now select Troubleshoot > Advanced Options > Command Prompt.
• After that, type “rstrui” and hit Enter to execute the command which will start the System Restore process.
• Once it’s done, restart your computer.

Option 2 – Boot your computer in Safe Mode

You can try to tap the F8 key if you have it enabled in your Windows 10 computer, as you start your system to boot into Safe Mode. Once your computer is in Safe Mode, you can access the Start Menu and the Mouse and Keyboard. Aside from that, you can also access your files and other built-in tools in Windows such as Command Prompt, PowerShell, Computer Manager, Device Manager, Event Log Viewer, and many more. On the other hand, if you haven’t enabled the F8 key, you can just go to the Advanced Startup options to boot your computer into Safe Mode. Once you’re there, select Troubleshoot > Advanced Options > Startup Settings > Restart > Tap the number 4 key. After that, your computer will restart in Safe Mode. If you want to reboot into Safe Mode with Networking instead, you can tap the number 5 key and for Safe Mode with Command Prompt, tap the number 6 key. Once your computer is in Safe Mode, you can use any of the built-in tools to restore your computer or troubleshoot the problem that’s causing your computer to get stuck at the “Preparing to configure” screen.

Option 3 – Try to repair your corrupted profile via Registry

In this third option, you can try to repair the corrupted profile using the Registry but before you proceed, take note that you can only try this if you can boot into your desktop and if you can, make sure to create a System Restore Point and then follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Then type “Regedit” in the field and hit Enter or click OK to open the Registry Editor.
• Next, go to this registry key: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionProfileList
• Once you’ve opened the registry key, you should see a list of all the user profiles on your computer. Now click on each S-1-5 folder and look for the “ProfileImagePath” entry and double click on it to check which user account it is related to. You will see a path like “CUsersACK” where “ACK” is the username.
• You should know which of the user account is corrupted. Just look for a key named “RefCount” and change its Value data to “0” and click OK. And if it isn’t available, simply right-click on the right pane and create it.
• After that, double click on the key named “State” and make sure that the Value data is “0” and click OK.
• Exit the Registry Editor and restart your computer to apply the changes made.

Option 4 – Try to use installation media to boot and repair your computer

Another thing you can try to resolve the issue is to use the Windows installation bootable media so you can boot and repair the operating system. To use it, follow these steps:

• You need to first create an installation media which has the dame version of the operating system installed in your computer.
• After that, once you reach the Install Windows screen, click on the “Repair your computer” link.
• Wait until the repair is completed and then shut down your computer
• Now once your computer has restarted, check if it can now boot properly.

When performing a Windows Backup to the NAS device (backup to a network share) that is running Samba, fails with an error message The backup failed, The version does not support this version of the file format (0xC03A0005). The problem occurs because of a conflict with the VHD file that is created by Windows Backup and is mounted during the process. There are three types of VHD files:

1. Fixed,
2. Expandable
3. Differencing

If the VHD file is a sparse file that is not supported by the native VHD driver, the mounting will fail, and you will get this error. An example VHD file is one that keeps expanding depending on the backup size. The problem occurs only in the case of  File Level backup (file/folders in a volume) but not on the block level backup as the vhd file is never mounted. However, in the case of File Level Backup, the vhd is mounted, created by Windows Backup, which does not support the mounting of sparse files.

The solution is to use Strict Allocate: option in the smb.conf file

Login to SMB using SSH. Open the configuration file using the VI editor located at /etc/samba/smb.conf. If the option is not there, you can manually add strict allocate = yes which will make sure there are no sparse file that is created.

New malware with extensive spyware capabilities steals data from infected Android devices and is designed to automatically trigger whenever new info is read to be exfiltrated. The spyware can only be installed as a 'System Update' app available via third-party Android app stores as it was never available on Google's Play Store. This drastically limits the number of devices it can infect, given that most experienced users will most likely avoid installing it in the first place. The malware also lacks a method to infect other Android devices on its own, adding to its limited spreading capabilities. However, when it comes to stealing your data, this remote access trojan (RAT) can collect and exfiltrate an extensive array of information to its command-and-control server. Zimperium researchers who spotted it observed it while "stealing data, messages, images and taking control of Android phones."

What happens when malicious software is installed

"Once in control, hackers can record audio and phone calls, take photos, review browser history, access WhatsApp messages, and more," they added. Zimperium said its extensive range of data theft capabilities includes:

• Stealing instant messenger messages;
• Stealing instant messenger database files (if the root is available);
• Inspecting the default browser's bookmarks and searches;
• Inspecting the bookmark and search history from Google Chrome, Mozilla Firefox, and Samsung Internet Browser;
• Searching for files with specific extensions (including .pdf, .doc, .docx, and .xls, .xlsx);
• Inspecting the clipboard data;
• Inspecting the content of the notifications;
• Recording audio;
• Recording phone calls;
• Periodically take pictures (either through the front or back cameras);
• Listing of the installed applications;
• Stealing images and videos;
• Monitoring the GPS location;
• Stealing SMS messages;
• Stealing phone contacts;
• Stealing call logs;
• Exfiltrating device information (e.g., installed applications, device name, storage stats).

How does it work?

Once installed on an Android device, the malware will send several pieces of info to its Firebase command-and-control (C2) server, including storage stats, the internet connection type, and the presence of various apps such as WhatsApp. The spyware harvests data directly if it has root access or will use Accessibility Services after tricking the victims into enabling the feature on the compromised device. It will also scan the external storage for any stored or cached data, harvest it, and deliver it to the C2 servers when the user connects to a Wi-Fi network. Unlike other malware designed to steal data, this one will get triggered using Android's contentObserver and Broadcast receivers only when some conditions are met, like the addition of a new contact, new text messages, or new apps being installed. "Commands received through the Firebase messaging service initiate actions such as recording of audio from the microphone and exfiltration of data such as SMS messages," Zimperium said. "The Firebase communication is only used to issue the commands, and a dedicated C&C server is used to collect the stolen data by using a POST request."

Camouflage

The malware will also display fake "Searching for the update.." system update notifications when it receives new commands from its masters to camouflage its malicious activity. The spyware also conceals its presence on infected Android devices by hiding the icon from the drawer/menu. To further evade detection, it will only steal thumbnails of videos and images it finds, thus reducing the victims' bandwidth consumption to avoid drawing their attention to the background data exfiltration activity. Unlike other malware that harvests data in bulk, this one will also make sure that it exfiltrates only the most recent data, collecting location data created and photos taken within the last few minutes. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

There are times when you encounter some issues while your Windows 10 computer. One of the errors you can encounter in the update process is the “Something went wrong, error code 0x8007042B”. This kind of error might be caused by several reasons and it could also pop up in lots of cases like upgrading to a new feature update or a new build using the Media Creation tool or Windows Update Assistant. There are times when the Windows Update error code 0x8007042B is followed by another error code like 0x2000d. Whatever the extra error code that follows, the core issue still remains the same. To resolve the problem, here are some options that could help. And while going over these troubleshooting tips, you have to keep clicking the Update button right after you carry out a troubleshooting option.

Option 1 – Try to restart the Background Intelligent Transfer Service

The Background Intelligent Transfer Service or BITS is a part of the Windows Update service and is the one that manages the background download of Windows Update, as well as scans for new updates and so on. And if Windows Update is experiencing some problems, you can try restarting BITS but make sure that you have admin privileges to do so.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “services.msc” in the field and hit Enter to open Windows Services.
• From the list of Services, look for the Background Intelligent Transfer Service and double-click on it to open Properties.
• After that, you need to set the Startup type to “Automatic (Delayed Start) and click on Apply.
• Now click the Stop button to stop BITS and then click the Start button to restart the service.
• Click OK to save the changes made and then restart your PC.

Option 2 – Try creating Windows 10 ISO media

In this option, you will have to create a Windows 10 bootable media and use it to install the latest Windows 10 version. The most user reported that this option works and the reason why it does have something to do with the Windows Update client since the Windows Updates downloaded from the regular Windows Update client seems to create issues such as the Windows Update error code 0x8007042B. However, issues like this one don’t occur when the very same Windows Updates are downloaded and installed via an ISO file. Take note that when using a Windows ISO file, you will be asked to choose what you want to do with the previous settings and apps. A lot of users opted for the “Not to keep the old Windows settings” option which has resolved the issue. So if you want to keep the previous settings then you must try to update Windows first while keeping the old settings. However, if it doesn’t work, you have to try installing the latest version of Windows without keeping the previous settings.

• Click this link and then click the Download Tool Now button.
• Next, click the “Use the tool to create installation media (USB flash drive, DVD, or ISO file)…” option and follow the next given instructions on the screen.
• Now select the ISO file option in step 5.
• After that, you should now have an ISO file.
• Next, go to the location where you’ve downloaded the ISO file.
• Then right-click on the Windows 10 ISO file and select the Open with option and then select File Explorer.
• Now click on “setup.exe” and follow the next instructions that appear on the screen. When asked, you have to select either the Nothing (clean install) or the Keep personal files only option. Take note that you must not select the “Keep personal files, apps, and Windows settings since it doesn’t really work.

Option 3 – Run the DISM tool

You can run the DISM tool as well to help fix the error code 0x8007042B during Windows Update. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt with admin privileges.
• Then type in the following commands and make sure to hit Enter right after you type each one of them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • exe /Online /Cleanup-image /Restorehealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 4 – Perform a System File Checker scan

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the Windows Update Error 0x8007042B to appear. 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 5 – Run the Windows Update Troubleshooter

You might also want to run the Windows Update Troubleshooter as it could also help in fixing Windows Update Error 0x8007042B. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 6 – Contact Microsoft Support for assistance

If you’re at your wits’ end in trying to update your Windows 10 computer, you should consider contacting Microsoft Support for help as they can offer you various options that would make fixing Windows Update Error 0x8007042B a lot easier and faster.

Stop Running This Script Error - What is it?

"Stop Running This Script" Error is a Windows Internet Explorer error message that is displayed in the following format with a yes and a no button:

Stop running this script?

A Script on this page is causing your web browser to run slowly.  If it continues to run, your computer might become unresponsive. This occurs when some scripts take an excessive amount of time to run. To be precise, there are some websites that use JavaScript, JQuery, and Active X scripts to run. These scripts are notorious for taking too much time to run. So, if you use the Internet Explorer as your web browser, then by default if the website takes a long time to load, the ‘Stop running this script error will be triggered. Other than this, if you are scripting an Active X control on the web page to transfer a very heavy file or run a huge database query, this may cause delays and lead to the error display. However, if you use Firefox, then the ‘Stop running this script error code will be promoted as ‘Unresponsive Script’ error.

Solution

Error Causes

The ‘Stop running this script error code’ is triggered due to multiple reasons. These include:

• Webpage programming errors
• Running a pop-up killer
• Spyware and viral infection
• Active X control errors

Further Information and Manual Repair

Here are some of the best methods that you can try to resolve Internet Explorer’s ‘stop running this script error’ on your PC:

1. Change the Internet Explorer Settings

This can be done by opening Internet Explorer and in the top menu, click on Tools, and then go to Internet Options. Now click on the Advanced Tab option. Locate where it says ‘Disable Script Debugging’. Once you find it uncheck the box beside it. Now close the browser and restart your PC. Access the same website on your IE web browser and see if the website opens. If it does, then the error is resolved. However, if it doesn’t, then you the underlying causes for the stop running this script error message could either be spyware or ActiveX control error.

2. Download Restoro

Whether the error occurs due to spyware invasion of Active X control error, it is advisable to download Restoro on your PC. This is a next-generation, innovative, and multi-functional PC repair tool that has several powerful utilities deployed together in one program. Plus you don’t have to get into the technicalities of resolving Active X control issues. Restoro is safe, bug-free, and efficient. It has a user-friendly interface and simple navigation which makes it quite easy for all levels of users to operate. It is compatible with all Windows versions including Windows 7, 8, XP, Vista, 8.1, and 10. This PC repair tool is a one-stop solution for all your script error repair needs. It includes the following utilities: a registry cleaner, a system stability detector, and an ActiveX control error scanner. It simultaneously scans for ActiveX control errors too. So, if the IE script error is triggered by ActiveX control issues, it resolves them too. To fix the ‘stop running this script’ error code on your PC, click here to download Restoro

Error Code 28- What is it?

The error code 28 is a driver error. This is one of the many device manager error codes. When this error occurs on your computer, the following message is displayed:

“The drivers for this device are not installed. (Code 28)”

Another driver device error message you might encounter is error code 41. 

Error Causes

Error 28 occurs because of unsuccessful device driver installation. This usually happens when you try to update new drive versions on your system. It is advisable to repair this error right away as it can hamper your ability to use certain hardware. For example, if error 28 occurs due to the unsuccessful installation of the USB driver, then it if not fixed and resolved it may prevent you from using hardware devices. Unsuccessful driver installation means you either didn’t install it properly or your computer has registry issues. If it’s the registry then you must fix it without any delay because it can expose your PC to serious threats like system crash and failure. To avoid such inconvenience, repair it.

Further Information and Manual Repair

When it comes to repairing the error code 28, here’s what you can do: Simply go to the control panel and click on the Device Manager option:

• In the details pane with the list of devices, locate the device for which you want to reinstall the driver software.
• Double click on it to open the properties dialog box.
• Now click on the driver tab and then click update driver.

After updating, try using that device again if it doesn’t work and shows the error code 28 on your computer screen then this means the underlying cause is the registry.

Resize icons on desktop in Windows 10 in a matter of seconds! Hello everyone and welcome to today's quick tip. If you have ever been dissatisfied with icon size on your desktop and any of the default sizes like small, medium large, etc have not been appropriate know that there is a quick way to resize icons on your desktop in between sizes. All that you have to do in order to use this built-in feature is: Press and hold CTRL and scroll with the mouse. That's it! Find your appropriate size for icons and enjoy.