Clipboard history in Windows 10

Error Code 35 - What is it?

Error Code 35 is a typical Device Manager error. It indicates information missing to properly configure your device.  Error code 35 is usually displayed in the following format:

“Your computer's system firmware does not include enough information to properly configure and use this device. To use this device, contact your computer manufacturer to obtain a firmware or BIOS update. Code 35”

Solution

Error Causes

The 2 common reasons for Device Manager error code 35 are:

• Outdated BIOS
• Mis-configured, corrupted, or outdated Drivers

No matter what the reason may be, it is advisable to resolve the problem immediately without any delay otherwise you will be unable to use your hardware device.

Further Information and Manual Repair

Below is the list of the most effective and easy to perform solutions to resolve error code 35 on your PC. These solutions do not require any technical knowledge or understanding. Simply follow the instructions to resolve this error code.

Method 1 - Update the BIOS

BIOS (Basic Input/Output System) is the embedded software on the computer’s motherboard.

Though not all PCs have the same BIOS manufacturer, but the steps for updating the BIOS are similar for all versions. Before you get started with the updating process, first identify your current BIOS version.

• For this, go to the start menu and type msinfo32, and press enter.
• Now click System Summary to view your BIOS version. Here you will see the version number and date.
• Now check your PC motherboard manufacturer’s website to download the BIOS update for the model you own. Also, download any Read Me Files and documentation. These contain guidelines and precautions that you should know before you update.
• Backup all your data and existing BIOS before you update the BIOS version. This will keep your data protected in case the attempt to update BIOS fails.
• Also, when updating, make sure to use an uninterruptible power supply. Remember power outage or even a small power fluctuation can corrupt the BIOS which is something you don’t want.
• Now it’s time to perform the update. Run the downloaded installer for the BIOS updating software. Double click on the executable file.
• Look for a button names Update, Flash, or Run.
• Click on it to start updating the new version
• After the update is complete, your computer will restart automatically.

This will hopefully resolve the problem. However, if the error still persists then there is a possibility that the error code is related to outdated drivers. To resolve, try method 2.

Method 2 - Download Driver Assist to Update Drivers Automatically

Update drivers to repair error code 35 on your PC by simply downloading DriverFIX. This is a cutting-edge program deployed with an intelligent programming system.

It is compatible with all Windows versions.

It scans your PC for problematic drivers and updates them with the latest and compatible versions automatically and in a few seconds thereby repairing all Device Manager error codes including error code 35 generated due to outdated/corrupted drivers.

In addition to this, it updates all device drivers on a regular basis, so you don’t have to stress over and keep a track of what drivers on your PC need to be updated and when.

Click here to download DriverFIX to resolve Device Manager error code 35 today!

Kernel32.dll Error - What is it?

To understand Kernel32.dll error properly, here’s what you need to know first: in the Windows operating system, the system32 directory plays a vital role. Inside this directory, there is an element called Kernel32.dll. A DLL (dynamic link library) is a library that contains codes and data that are used by more than one program at the same time. The role of the Kernel32.dll file is to handle memory management and I/O (input and output) operations. Malfunctioning of this file results in a Kernel32.dll error message which leads to program or application failure.

Error Causes

Kernel32.dll files can be attributed to several reasons like:

• Missing or damaged Kernel32.dll files
• Registry corruption
• .Dll files misconfiguration if programs are installed or uninstalled.
• Viral infection or malware attack

It is advisable to repair the Kernel32.dll error immediately to avoid inconvenience and serious computer damages like program lockouts, system failure, freeze, and crash.

Further Information and Manual Repair

All causes for the Kernel32.dll error are linked with the registry. The registry is the major database of your system that stores all the activities you perform on your system. It saves both important data and unnecessary files in the RAM (Random Access Memory) including the junk files, temporary internet files, and obsolete files such as files of the deleted/uninstalled programs. These files accumulate a lot of memory space. It leads to disk fragmentation, data overload, missing and damaged DLL files, and eventually registry corruption. Other reasons for registry issues that trigger Kernel32.dll errors on your system could be malicious software like viruses, adware, and malware. These also corrupt the registry and damaged DLL files.

Kernel32.dll Error Solutions

There are two ways to resolve the Kernel32.dll error on your PC, one is to install two separate tools registry cleaner and an antivirus and run them individually to scan your system and repair it. This option is time-consuming and besides if antivirus software is notorious for slowing down systems. So by downloading a separate antivirus you may have to sacrifice your system’s speed.

Microsoft Designer, a new application developed by Microsoft will bring design backed with DALL-E 2, an AI image creation open-source software. The new app is shown as a dedicated graphic design tool that will help you in the creation of stunning social media posts, invitations, digital postcards, graphics, and more, all in a flash.

Use of the application will be by typing headings and then typing text into the prompt to generate a background image. Since Microsoft uses DALL-E 2 for image creation output should be fairly good but if you wish you will be able to use your own images instead of using AI to generate one.

The designer will be a free application once it is ready and it already has a web preview version, also free but with a waitlist. There will be premium features inside the app once it is released that will be available to Microsoft 365 Personal and Family subscribers. Microsoft also wants to add a version of a designer directly to the Edge browser as well.

TPM 2.0 requirement for Windows 11 has produced a lot of discussions since it was announced. A lot of somewhat older hardware seems to be left behind with this decision from Microsoft. So naturally, when something like this is announced, especially when it is stated it is the must-have thing, people find a way to break it and to prove it is not the case. In that spirit, I am proud to present you with not one but three-way you can install Windows 11 on hardware that does not has TPM 2.0. Please note that by bypassing this you will not be able to use some Windows 11 features tied to modules like Device encryption, vTPM in Hyper-V, and all TPM-related services. I will cover methods from the most simple and straightforward ones to the more complicated using registry editor.

Bypass TPM with changing installation media

For this method to work you will need both Windows 10 ISO and Windows 11 ISO since it will require some file copying between them. You will also need Rufus or another tool to make a new installation media once files are copied All you have to do in this method is to go into your Windows 10 ISO and delete the install.esd, then just copy install.wim from Windows 11 installation media into the same place, and you are done. Make install ISO with Rufus and install Windows 11.

Change DLL on installation media method

For this method, you will need everything like in the previous one and the process is almost the same, but this time instead of migrating the whole installation file, we will just replace the appraiserres.dll file. Copy appraiserres.dll file from your Windows 10 installation media over the same file on Windows 11 installation and you are good to go.

Bypassing TPM via registry editor

If for some reason previous easy solutions have not worked for you do not lose hope just yet, there is one more way you can bypass TPM. In this given method you will not need Windows 10 installation media but the process is a little more complicated than previous ones.

1. Create Windows 11 media installation
2. Start the installation process
3. Click the Next button.
4. Select region, language, and time when asked. You can change these settings later.
5. Click the Install now button.
6. If your device was already activated, click the I don’t have a product key option to continue.
7. Click the Next button. Select the edition of Windows. When you’re installing the OS on an existing device, Windows won’t activate if you select the incorrect edition.
8. Click the Next button.
9. Select the I accept the license terms option and click next.
10. Select Custom: Install Windows only (Advanced)
11. During the Windows installation screen, now you will see a message stating that the PC can’t run Windows 11 if you do not have TPM 2.0
12. On this screen, press SHIFT + F10 to open Command Prompt window.
13. Launch the registry editor, type regedit.exe in Command Prompt, and press ENTER
14. Create a new key “LabConfig” by right-clicking on the Setup key and select New > Key under HKEY_LOCAL_MACHINE\SYSTEM\Setup.
15. Type LabConfig and press ENTER.
16. Right-click on the LabConfig key.
17. Select New > DWORD (32-bit) value.
18. Create two values: BypassTPMCheck and BypassSecureBootCheck.
19. Set their DWORD32 value to 1.
20. Press ENTER.
21. Close the Registry Editor.
22. Type exit in the Command Prompt and press ENTER or close its window.
23. Press the back button in the Windows installation setup if it still says “This PC can’t run Windows 11”.
24. Accept the terms & conditions.
25. Select Custom: Install Windows only (Advanced) option and configure the partition with the current installation.
26. Click the Next button.
27. Finish Windows 11 installation

KMODE_EXCEPTION_NOT_HANDLED – What is it?

Some users installing or upgrading to Windows 10 experienced the theKMODE_EXCEPTION_NOT_HANDLED Blue Screen of Death (or commonly known as BSOD) error. This error can be due to different types of things, ranging from software to driver issues. When you experience this BSOD error while trying to install Windows 10, it will prompt you to restart your computer every single time you experience it. In most cases, you will also not be able to proceed with the Windows 10 set-up.

Solution

Error Causes

The “KMODE_EXCEPTION_NOT_HANDLED” error is normally caused by:

• Hardware incompatibility
• A faulty device driver or system service

Further Information and Manual Repair

You won’t be able to successfully upgrade or set up Windows 10 if you continue to encounter this BSOD error. Note that this error will always prompt your computer to restart every time it happens, preventing you from completing the Windows 10 set-up.

If you’re not tech-savvy or not capable of debugging this issue, it’s highly advisable to proceed with the basic troubleshooting techniques available in this link.

After troubleshooting, below you’ll find a few solutions to rectify the issue.

Method 1 – Check The Cause of The BSOD Error

Two common causes of the KMODE_EXCEPTION_NOT_HANDLED issue are hardware incompatibility and faulty device driver or system service.

If you experience this error, check first if any of your newly installed hardware is compatible with Windows 10. You can find the required hardware for Windows 10 from this link. 

If all your hardware is compatible with Windows 10, you might need to check the device driver or system service. Review the bug check message. If any of the drivers you have is listed in the message, either disable or uninstall them before upgrading or setting up Windows 10.

You might also find it useful to check the System Log available in the Event Viewer for other error messages that can help you figure out the driver or device that’s causing the error. Running hardware diagnostics can also be useful.

Method 2 – Disable (or preferably uninstall) Software Before Upgrading

If you’re upgrading Windows 10 from Windows 7 or Windows 8.1, you might need to disable or uninstall the software first. First, try uninstalling your Antivirus utility before starting the upgrade. Restart a few times before starting the Windows 10 installation. If you’re upgrading using the Windows 10 update, make sure that you disconnect from your Wi-Fi or Internet LAN (Ethernet) connection as soon as the download reaches 100% before attempting to start the set-up. Other users also reported that the cause of the KMODE_EXCEPTION_NOT_HANDLED issue is BitDefender. If this is what happened in your case, it will show in the error message such as KMODE_EXCEPTION_NOT_HANDLED (bdselfpr.sys). Users reported that a common solution for this is renaming the file. In the case of BitDefender, try renaming it to bdselfpr.s__. However, make sure to do this cautiously. Sometimes, renaming a file will even do more damage than good.

Method 3 – Disable/Disconnect From Hardware

If you’re connected to any general USB devices (such a smart card reader), disable it. If your computer is connected to other external devices, disconnect all of them. Examples of this include gaming controllers, printers, external hard disk, USB keys, and other non-essential devices).

Method 4 – Other Troubleshooting Steps

Other troubleshooting steps include:

• Upgrade using an .ISO file, instead of directly upgrading from Windows Update. When you do this, make sure you’re disconnected from the Internet during installation. If the process started and you forgot to disconnected, it’s best to restart the installation.
• If you’re connected to a domain while trying to set up Windows 10, disconnect and use a local account.
• If you’re using a SCSI hard disk, connect a thumb drive with the drivers for your storage device. While Windows 10 is setting up, click on the Custom Advanced Option. Using the thumb drive, use the Load Driver command to load the SCSI drive.
• Another possible cause of this error is due to BIOS incompatibility. BIOS issues can be solved by upgrading your version of your system BIOS. If you don’t know how to do this, refer to your BIOS manufacturer’s website.

Method 5 – Use A Trusted Automated Tool

If you still experience the error after doing the methods above, you might want to try a powerful and trusted automated tool to fix the job.

In previous versions of Windows changing the system, the font was a pretty straightforward process, but it seems Microsoft did not want this feature to keep for whatever reason and there is no option as of the time of the writing of this article to do it in standard options in Windows 10. But do not worry, you are still able to customize your Windows and choose which font would you like to see inside it in all of its dialogs. You can choose whichever font you desire, the only prerequisite is it to be installed on your system. This guide will require you to change values in the registry of Windows itself so please follow step-by-step instructions and always make a backup of the registry before changing it in order to prevent some permanent Windows issues. All of that being said, let's start.

Setting new font

First thing is to open notepad, in the notepad paste the next block of code:

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts] "Segoe UI (TrueType)"="" "Segoe UI Bold (TrueType)"="" "Segoe UI Bold Italic (TrueType)"="" "Segoe UI Italic (TrueType)"="" "Segoe UI Light (TrueType)"="" "Segoe UI Semibold (TrueType)"="" "Segoe UI Symbol (TrueType)"="" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes] "Segoe UI"="NEW_FONT"

Where in "Segoe UI"="NEW_FONT" instead of NEW_FONT you need to write the exact name of the font that you wish to use as a system font. Once you have replaced the default system font with your desired one, go to File and save as, from file type drop-down menu, choose all files and save this file as .REG type giving it whatever name you wish. When the file is saved, close notepad, right-click on the saved file and choose the merge option. Confirm with YES and click on OK. Reboot your system and your Windows will now use the font of your choice as its default system font.

Restoring default font

If you wish to return the old default system font as it was, follow the same steps but in your notepad paste this code:

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts] "Segoe UI (TrueType)"="segoeui.ttf" "Segoe UI Black (TrueType)"="seguibl.ttf" "Segoe UI Black Italic (TrueType)"="seguibli.ttf" "Segoe UI Bold (TrueType)"="segoeuib.ttf" "Segoe UI Bold Italic (TrueType)"="segoeuiz.ttf" "Segoe UI Emoji (TrueType)"="seguiemj.ttf" "Segoe UI Historic (TrueType)"="seguihis.ttf" "Segoe UI Italic (TrueType)"="segoeuii.ttf" "Segoe UI Light (TrueType)"="segoeuil.ttf" "Segoe UI Light Italic (TrueType)"="seguili.ttf" "Segoe UI Semibold (TrueType)"="seguisb.ttf" "Segoe UI Semibold Italic (TrueType)"="seguisbi.ttf" "Segoe UI Semilight (TrueType)"="segoeuisl.ttf" "Segoe UI Semilight Italic (TrueType)"="seguisli.ttf" "Segoe UI Symbol (TrueType)"="seguisym.ttf" "Segoe MDL2 Assets (TrueType)"="segmdl2.ttf" "Segoe Print (TrueType)"="segoepr.ttf" "Segoe Print Bold (TrueType)"="segoeprb.ttf" "Segoe Script (TrueType)"="segoesc.ttf" "Segoe Script Bold (TrueType)"="segoescb.ttf" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes] "Segoe UI"=-

Reboot your system and your Windows will now revert the font of your choice as its default system font.

Error Code 0x80070490 - What is it?

When downloading a Windows update, it is important to remember that these updates are what keeps your computer safe. Some users have reported seeing error code 0x80070490 when allowing updates for their Windows PC. This error code may appear when the user is trying to connect to the update site for Windows and maybe a result of a corrupted CBS manifest. Having this error code will not only stop the update of the system, but it will also certainly halt any work being done with the computer. Quite a few Windows users have written in complaints about this error while updating from any prior Windows update to Windows 10.

Common symptoms include:

• While a user is performing the updates, the Windows computer will stop running the updates, and it will show the error code 0x80070490.
• Windows updates will not install any new features and will not install security patches.
• The computer will not continue with the Windows update, and it may revert back to the previous state that the computer was in, prior to attempting the updates.

Error Causes

There is not a lot known about what exactly causes the error code 0x80070490, but it is something critical that makes Windows abruptly stop its updates. It could be caused by a simple glitch in the computer system, or it could be caused by a larger problem. One thought is that the CBS (Component-Based Servicing) manifest can be corrupt. Another thought is that the computer's anti-virus software may be interfering with the computer's ability to perform the necessary updates.

Further Information and Manual Repair

There is very little information known about error code 0x80070490 and why it exists, but there are a few methods in which to correct it. Users should be careful when trying to fix this error themselves. If the user feels that the methods are too complicated or they are uncomfortable taking it on themselves, they should contact a Windows repair technician to fix the problem. Not all methods listed will suit the user's needs, but it is dependent upon the problem at hand as to which method will be the best fit to fix the error code. If these steps are taken and the error is not corrected, it is vital to contact the Windows repair technician.

Method One: Creating a new local account

Create a new local account on the computer, and allow administrator privileges on it. Next, move all of your documents and personal files to the new account. Delete the old account (you will no longer be using this) and switch over to the new one. After switching to the new local account, add the Microsoft account to it.

Method Two: Delete user ID, Store cache from the registry

• You will need to open the Registry Editor. Do this by pressing the Windows Key and R, then typing in “Regedit”. After this is typed in, press Enter or click the OK button to start the registry editor.
• When this starts, you will need to navigate all the way to the following key on the left pane:
• HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionAppxAppxAllUserStore After this, find the key that is similar to this: S-1-5-21-1505978256-3813739684-4272618129-1016
• NOTE: this is just an example. The keys will be in a similar format but will not look exactly like this.
• Select all the keys that look like this, and then delete them. After these keys are deleted, close the Registry Editor and restart the computer.

Method Three: Check to see if BITS, MSI Installer, Cryptographic, and Windows Update Services are running

Press the Windows key and R. Then, type in services.msc. After the Services window starts up, find the following services:  BITS, MSI Installer, Cryptographic, and Windows Update Services. When these services are found, make sure that they are up and running. If one or more of these services is not running, make sure that they are started. To do this, select the service and then click on Start the Service.

Method Four: Windows Update Troubleshooting

Press the Windows key plus W and then type in “troubleshooting”.  Select Troubleshooting. On the top left corner, select View All. Click on Windows Update troubleshooter. After this, follow the on-screen instructions in order to run the troubleshooter. After the troubleshooter has run, the issue should be fixed.

Recently, a few users reported that they were unable to turn on their computers for some reason and at the same time their computers Computer makes a beeping noise couple of times or continuously whenever they try to turn them on. The sounds the computers are making can be quite annoying and it also signifies that there is something wrong with them. The problem might have something to do with the hardware inside of the computer system rather than Windows 10 itself. As you know, a computer is designed to deliver audible error sounds every time some part of the hardware is not properly working. For instance, if you hear a single beep, this indicates that your GPU is having some issues and if you’re hearing two beeps, it indicates that your RAM is not working properly, whereas three beeps that repeat after a pause when you turn on your computer means that there is something wrong with the system memory. On the other hand, if your computer is beeping continuously, this means that the problem lies with the processor. To fix this issue, here are some suggestions that might help but before you proceed, make sure that you know how to manage your computer’s hardware, if not, better have some expert do it for you.

Option 1 – Try checking the RAM

One of the basic things you can do in this kind of case is to check the RAM. Prepare some screwdrivers and dig into your PC and then look for the RAM slots and ensure that they are attached firmly. There are times when moving around your computer daily can cause certain components in your computer to become loose. Worst case scenario is that the RAM might be broken so really have to replace it.

Option 2 – Try checking the graphics card

After digging into your computer, check the graphics card and give it some good cleaning. As you know, you have to remove certain components like the graphics card regularly and clean them to help increase their lifespan and avoid errors in a startup. And if it turns out that the graphics card is broken, you have to replace it with a new one to fix the problem.

Option 3 – Try checking the processor

The processor is the brain of every computer so if it ends up not working, everything else is useless. Thus, you need to check it to see if it’s firmly attached and see if it needs some cleaning of dust and other debris. After that, try turning on your computer again. If it doesn’t work, then you might have to take your system to a technician to resolve the problem for you.

Error 0x80004005 - What is it?

Error 0x80004005 is a typical Outlook error. This error code occurs either when sending emails or receiving them. The error message may be displayed in either of the following formats:

‘Sending and receiving reported error "0x80004005": The operation failed.’ ‘This message could not be sent. Try sending the message again or contact your network administrator. The client operation failed. Error is [OX80004005- 0X0004B9-OXOO501].’

Error Causes

There are several causes for the error 0x80004005 such as:

• The Script Blocking Feature Enabled While Using Norton Antivirus
• Spyware
• Viruses
• Registry problems-Missing or corrupt registry keys

It is advisable to repair and resolve error 0x80004005 immediately as it may cause a great deal of inconvenience to you. This error may hamper your ability to receive and send emails from your Outlook account and lower your productivity too as you may be unable to communicate with your peers.

Further Information and Manual Repair

To fix error 0x80004005, you don’t have to wait for the network personnel or be a technical expert yourself. This may be a critical error but the good news is that it is easy to resolve. Here are some effective methods and quick fixes to resolve the error 0x80004005 instantly.

Method 1: Disable Script Blocking Feature in Norton Antivirus

After installing Norton Antivirus on your PC, if you start experiencing the Outlook error 0x80004005, then the best way to resolve it is to simply disable the script blocking feature. However, the downside of this is that by disabling this feature your PC will become vulnerable to viruses and malware.

Method 2: Disable the New-Mail Notification Feature in MS Outlook

If you don’t have Norton Antivirus downloaded on your PC, then try method 2. This method involves disabling the new-mail notification feature in MS Outlook. The error code 0x80004005 is often resolved by switching off this feature. Try it to see if it works. To disable the new-mail feature all you have to do is open your Outlook account and then go to the Tools menu, then go to Options and then select the ‘Preferences’ tab. After that click on the ‘Emails Options’ tab and then simply uncheck the check-box against ‘Display a notification message when new mail arrives’. To confirm changes press OK.

Method 3: Scan for Viruses

The error 0x80004005 may also be triggered due to viral infection or spyware. Such malicious software enters your PC through phishing emails and while downloading files and attachments. You may not be aware of this but your PC may be infected by viruses. It is important you remove them immediately as they can expose you to serious risks including privacy issues, identity thefts, data breaches, and more.

If you are using Windows PowerShell and it suddenly throws an error message saying, “File cannot be loaded because running scripts is disabled on this system”, then read on as this post will guide you on how you can fix this issue your Windows 10 computer. This kind of error in PowerShell is most likely due to the fact that your user account does not have the required permissions to execute the script. Although this does not mean that you need to have administrator-level permissions as it could also indicate that you have to be unrestricted to run these types of PowerShell scripts or cmdlets. Thus, to fix the error and carry out the task, you have to set the execution policy to be unrestricted. And to do that, you need to use the steps provided below as a reference. Step 1: To get started, you have to check what policies are set for the individual user groups on your computer by tapping the Win + X key combination or by right-clicking on the Start button and clicking on Windows PowerShell (Admin). You can also search for PowerShell in the Start Search and then right-click on Windows PowerShell and select Run as administrator. Step 2: If a User Account Control or UAC prompt appears, just click Yes to proceed. Once you’ve pulled up Windows PowerShell, type the following command to get the List of Execution Policy for all the scopes on your computer.

Get-ExecutionPolicy –List

Step 3: After you execute the command, it will give you a list of the User Groups as well as their Execution Policy status, and under the Scope column, look for “LocalMachine”. Once you find its Execution Policy you will notice that it’s either set to Undefined or Restricted. Step 4: Now that you’ve determined the Execution Policy, you need to set it to Unrestricted if it is set to Restricted. To do that, you have to enter the following command in the very same PowerShell window.

Set-ExecutionPolicy Unrestricted

Step 5: After you execute the command, you will see a message that asks for various permissions for which you either have to tap Y to say Yes to each one of the messages individually or tap the A key to say Yes to all the messages to once. However, if the command throws another error, you can just force the Execution Policy to change by executing the following command.

Set-ExecutionPolicy Unrestricted -Force

Step 6: Once you’re done, it will finally set the Execution Policy for the Windows PowerShell scripts as well as cmdlets to be Unrestricted and fix the “File cannot be loaded because running scripts is disabled on this system” error.