Logo

OOOOPS it seems that this page does not exist :(

Instead of feeling bad why don't you try our automated software ...
... or check some of our articles and tutorials.
Fix Windows Updates Error code 0x80246007
Downloading Windows Updates does not always go smoothly as you can encounter several issues like the “Some updates did not finish downloading, We will keep trying, Error code 0x80246007” error. In fact, this error can also occur on other Windows applications like OneNote. According to security experts, this error happens for many reasons. For one, it could be that the Windows Update database is corrupted. It could also be that there is another process that’s in conflict with the Windows Update components or there might be some issue with the Background Intelligent Transfer Service (BITS). Whichever the cause may be, you can fix it by following the solutions given below.

Option 1 – Delete the contents in the Temporary folder

You can also try deleting the contents in the Temporary folder – all the downloaded, pending, or failed Windows 10 updates. You can do that using the simple and easy steps below.
  • Tap the Win + R keys to open the Run dialog box.
  • Then type “%temp%” in the field and press Enter to open the Temporary folder.
  • After that, select all the folders and files within the Temp folder and delete all of them.

Option 2 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter is one of the things you can first check out as it is known to automatically resolve any Windows Update errors like Error code 0x80246007. 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 3 – Try renaming or removing the pending .xml file

The problem might be due to some pending .xml file so you need to rename or remove it. To do so, just go to C:/Windows/WinSxS folder. From there, look for a pending .xml file – you can either rename it or delete it. This will allow the Windows Update to delete any pending tasks and build a new and fresh update check.

Option 4 – Restart the Background Intelligent Transfer Service (BITS)

The Background Intelligent Transfer Service or BITS is a part of the Windows Update service that manages the background download of Windows Update, as well as scans for new updates and so on. Thus, if your Windows Update fails a couple of times, you might want to restart BITS. For you to do that, make sure that you have admin privileges.
  • Press the Win + R keys to open the Run dialog box.
  • Then type “msc” in the field and hit Enter to open Services.
  • After opening Services, look for the Background Intelligent Transfer Service from the list of services and then double click on it to open Properties.
  • Next, set the Startup type to Manual and click on the Start button. If it doesn’t help, you can try setting it to Automatic (Delayed) and then reboot your PC.

Option 5 – Run the DISM tool

Running the DISM Tool helps in repairing the Windows System Image as well as the Windows Component Store in Windows 10. 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 6 – Delete the files from the Software Distribution folder

The downloaded Windows Updates are placed in a folder called “SoftwareDistribution”. The files downloaded in this folder are automatically deleted once the installation is completed. However, if the files are not clean up or if the installation is still pending, you can delete all the files in this folder after you pause the Windows Update service. For complete instructions, refer to the steps below.
  • Open the WinX Menu.
  • From there, open Command Prompt as admin.
  • Then type in the following command – don’t forget to hit Enter right after typing each one of them.
net stop wuauserv net start cryptSvc net start bits net start msiserver
  • After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
  • Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.

Option 7 – Reset the Catroot2 folder

After resetting the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:
  • Type each one of the following commands.
net start wuauserv net start cryptSvc net start bits net start msiserver
  • After that, exit Command Prompt and restart your computer, and then try to run Windows Update once more.
Read More
Fix Unknown USB Device error message
USB devices are one of the commonly used devices every day – from plugging mobile devices for charging using pen drives, you are making use of USB drives. However, there are times when you might encounter an error message saying, “Unknown USB Device” as you plug your USB device on your Windows 10 computer. So if you encounter this kind of error message followed by either of the following explanations, read on as this post will give you a couple of suggestions you can check out to resolve the issue.
  • Device Descriptor Request Failed
  • Port reset failed
  • The device failed enumeration
  • Set address failed
  • Error code 43
You can fix this error using several ways. You can try changing the Power Options, update or roll back the USB drivers, turn off Fast Startup, or run the USB troubleshooter. Follow the options given below for more details.

Option 1 – Try to change the Power Options

  • Tap the Win + R keys to open the Run utility.
  • Then type “powercfg.cpl” and tap Enter to open the Power Options window.
  • Next, go to your selected power plan and click the “Change plan settings” option to open a new page.
  • From there, click on the “Change advanced power settings” option. This will open a new window where you can see various power consumption options.
  • Now look for the USB Settings option and expand it.
  • Then set the USB selective suspend setting to “Disabled” for both scenarios: On Battery and Plugged in.
  • After that, click on OK and restart your computer to apply the changes made.

Option 2 – Update or reinstall the Universal Serial Bus Controller driver

Since it could be a driver issue, you can try to update or reinstall the Universal Serial Bus Controller drivers using the Device Manager. Refer to the following steps:
  • First, click the Start button and type “device manager”.
  • Then click on the “Device Manager” from the search results to open it.
  • From there, look for the “Universal Serial Bus controllers” option and then right-click on each one of the USB drivers and select the Update Driver from the menu.
Note: If it is a regular USB drive, then it will be listed as a USB Mass Storage Device but if you have a USB 3.0 device, then look for a USB 3.0 Extensible Host Controller.
  • Restart your PC and then click the “Search automatically for updated driver software” option.
Note: If updating the USB Controller drivers didn’t work, you can try to reinstall them instead.

Option 3 – Try turning off Fast Startup

  • Tap the Win + R keys to open the Run dialog box and type in “control” to open the Control Panel.
  • Next, click on the Hardware and Sound section and click on Power Options.
  • Afterwards, select the “Choose what the power buttons do” option from the left side menu pane.
  • Now click on Change settings that are currently unavailable and uncheck the entry that says, “Turn on fast startup (Recommended).
  • Then click on Save Changes and restart your computer and see if it has fixed the problem or not.

Option 4 – Run the Hardware and Devices Troubleshooters

  • The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
  • After opening Settings, look for the Update and Security option and select it.
  • From there, go to the Troubleshoot option located on the left-hand side of the list.
  • Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
  • After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.
Read More
Guide to Quick Fix Error 0x0000007B,0xF78524

0X0000007B (0xF78d2524) - What is it?

If you are a laptop or a notebook user and you are trying to install Windows XP on it, you might come across 0x0000007B (0xF78524) error message. This error is a popular blue screen of death error and very similar to the error 0x0000007B.

Solution

Restoro box imageError Causes

The common causes of 0x0000007B (0xF78524) error code on your laptop might be:
  • File Corruption
  • Device Configuration Issues
  • Adware/spyware invasion
  • Incomplete Installations
  • Problem with your computer’s hard drive controller

Further Information and Manual Repair

Many people panic when they experience 0x0000007B (0xF78524) error on their laptops and notebooks simply because it is a blue screen of death error. The BSoD has this whole persona of being deadly computer errors that can almost cripple systems. If you have also experienced this error on your laptop, remain calm and follow the solutions given below to ensure you fix the error quickly without any hassle. Here are various ways to fix and resolve the BSOD error code 0x0000007B (0xF78524):
  1. Whether you have Lenovo IdeaPad Y550 or Dell Latitude E4300 or any other laptop for that matter, if device driver configuration is the cause of the error 0x0000007B (0xF78524), then all you need to do is start up your laptop and press F2 to enter BIOS. Now expand the ‘Drives’ section. After doing so, go to ‘SATA Operation’. SATA is the abbreviation for Serial Advanced Technology Attachment which enables mass storage devices like hard drives and optical drives to communicate with the motherboard by using a high-speed serial cable. For successful communication between devices, you need to configure SATA controller mode. Once you go to the ‘SATA Operation’ mode, change this from RAID AHCI to RAID ATA. Save changes and exit BIOS. This helps resolve the error 0x0000007B (0xF78524) in no time.
  2. Another way to fix this error is to download and install the 0x0000007B (0xF78524) repair tool. Once this tool is installed on your laptop, click the scan button. Once the scan is complete, you will see a list of errors; click the ‘Repair’ button to fix the errors found and then restart.
  3. The 0x0000007B (0xF78524) error may also occur due to the boot volume corruption. In such an event, it is advisable to run chkdsk command on the hard drive. This is recovery console command is used to check the hard drive, repair and recover data on the drive successfully.
Read More
Display driver nvlddmkm stopped responding
Users are reporting that randomly their screen will just go black for a second and come back. When this happens, it usually distorts any video currently on the screen; sometimes, they can resume working on the PC normally. However, when they view the event logs, they see the error message Display driver nvlddmkm stopped responding and has successfully recovered. In this article, we will address solutions to this issue and how to not have it again.
  1. Remove Aura iCUE plugin (applies to only ASUS motherboards)

    Some PC users discovered that iCue adds an Aura plugin for ASUS MOBOs. That, combined with EVGA Precision X1, was causing the error it seems – this was determined when the screen would turn off and on when opening EVGA x1 software. In this case, the issue was resolved by removing the Aura iCUE plugins.
  2. Change Power Management mode

    Right-click the battery icon on the notification area on the right of the Taskbar. Select Power Options. In the Power Options window, locate your current Power Plan. Select High performance, if that’s not your current power plan. Now, click on Change plan settings next to it. Now click on Change advanced power settings. Expand PCI Express section. Expand Link State Power Management. Now set power saving to Off for both On battery and Plugged in state. This would fix any issues caused by the low power of the video card. Click Apply > OK to save changes.
  3. Update graphics driver

    Go into device manager Expand display adapter section Right-click on adapter Click on update driver Reboot
  4. Rollback graphics driver

    Go into device manager Expand display adapter section Right-click on adapter Click on Roll back driver Reboot
  5. Uninstall and reinstall graphics card driver

    Go into device manager Expand display adapter section Right-click on adapter Click on Uninstall device Reboot
  6. Replace the graphics card

    If everything else failed, replace the graphic card
Read More
Fix Dism.exe error 1392 in Windows 10
Dism.exe error 1392 is usually displayed whenever a file or directory is corrupted, and unreadable. The location specified in the error message states that some temporary files are corrupt. Since the files are only temporary, you could delete the mentioned file in the error message and check if the issue persists. The error is caused by missing system files or broken corrupt data, which should be fixed as soon as possible. Taking action should prevent further hardware and app damage, as this can lead to system crashes, data loss, or hardware failure in most cases.
  1. Temporarily disable the antivirus program

    Antivirus applications are well known that they can detect certain things as false positives and quarantine them or cut their system access, to make sure that this is not the case in this situation, disable your antivirus and try the operation again.
  2. Perform an SFC scan

    Press ⊞ WINDOWS + X to open the windows menu Click on Command prompt (admin) In the command prompt window type: sfc /scannnow and press ENTER Wait for the operation to complete Reboot
  3. Run Check disk to check and fix disk errors

    Press ⊞ WINDOWS + X to open the windows menu Click on Command prompt (admin) In the command prompt window type: chkdsk /f c: where c: is hard drive with issue and press ENTER
  4. Scan your computer for malware

    Malware and other malicious software can be a problem for this type of behavior, run your security's software scan on the whole system and remove any found malware.
  5. Perform a system restore

    If anything else failed run system restore and bring Windows back to a date when everything was working fine.
Read More
A required device isn’t connected
If you are currently facing the “A required device isn’t connected or cannot be accessed” error with codes 0xc0000185, 0xc0000225, 0xc0000001, 0xc00000f, and 0xc000000e on your Windows 10 computer, worry not for this post will help you resolve this problem. All these error codes point out the same thing – your computer needs to be repaired. Some of these error codes are related to the “winload.efi” file which means that you are using the UEFI system. This file also loads up important drivers in order to start the Windows Kernel. And if you got a remark from any of these error codes indicating that there is a hardware failure or that the driver configuration is incorrect, then you must physically check if the wires are connected properly. This kind of error occurs mostly when your computer wasn’t able to locate the system files that are needed to boot up your computer. Thus, the only way to fix this problem is to correct the boot record. It is recommended that you utilize the “/RebuildBCD” option in order to rebuild the BCD files. To do so, follow these steps:
  • You can start by booting into the installation environment for Windows 10 from an installation media.
  • After that, click on Repair your computer and on the blue screen, select Troubleshoot and then select the Advanced options menu.
  • From there, select Command Prompt and once you open it, enter each one of the commands given below by sequence.
    • bootrec /FixMbr
    • bootrec /FixBoot
    • bootrec /ScanOS
    • bootrec /RebuildBcd
  • Once you’re done executing the commands given above, type “exit” to close the Command Prompt window and then restart your computer and see if it fixed error code 0xc000014c.
On the other hand, if rebuilding the BCD using the /RebuildBCD option didn’t help, you can try a crude way to rebuild the boot record from scratch. You can do that by following the given steps below which will export and delete/backup the BCD available in the system.
  • Go to the Advanced Recovery Mode.
  • From there, go to Command Prompt and execute the commands given below and make sure to enter them one after the other.
    • bcdedit /export C:BCD_Backup
    • c:
    • cd boot
    • attrib bcd -s -h –r
    • ren c:bootbcd bcd.old
    • bootrec /RebuildBcd
If it still didn’t help, then troubleshoot the problem further with the help of the following instructions.

Option 1 – Disable the Secure Boot in the BIOS

Disabling the Secure Boot in the BIOS settings is definitely recommended to resolve the error. To disable Secure Boot, here’s what you have to do:
  • First, boot your computer into Windows 10.
  • Next, go to Settings > Windows Update. From there, check if there is anything that you have to download and install if you see any available updates. Usually, OEMs send and update the list of trusted hardware, drivers, and operating systems for your computer.
  • After that, go to the BIOS of your computer.
  • Then go to Settings > Update & Security > Advanced Startup options. If you click on Restart Now, it will restart your computer and give you all the advanced options.
  • Next, select Troubleshoot > Advanced Options. As you can see, this screen offers you further options including System restore, Startup repair, Go back to the previous version, Command Prompt, System Image Recovery, and UEFI Firmware Settings.
  • Select the UEFI Firmware Settings which will take you to the BIOS.
  • From there, go to the Security > Boot > Authentication tab where you should see Secure Boot. Note that every OEM has its own way of implementing the options so it varies.
  • Next, set Secure Boot to Disabled and set Legacy Support to On or Enabled.
  • Save the changes made and exit. Afterward, your computer will reboot.

Option 2 – Run System File Checker

You could also run a System File Checker or SFC scan. All you have to do is select Command Prompt from the Advanced Options. Once you’ve opened Command Prompt, type the “sfc /scannow” command and tap Enter to execute it.

Option 3 – Disable the Early Launch Anti-Malware Protection

  • You need to restart your computer in the Start Menu first while holding down the Shift key on your keyboard.
  • After that, it will restart your computer to Startup Settings.
  • Now ensure that the 8th option is labeled as “Disable early launch anti-malware protection.
  • Then tap the F8 key since the aforementioned option above is listed at number 8. This should launch and load Windows on your PC with the Early Anti-malware protection disabled for that session only when you try to carry out the same task and then check if the error related to the Winload.efi file is now fixed.

Option 4 – Try to run Automatic Startup Repair

In this option, you need to boot your computer into the Advanced Startup Options and from there, run the Automatic Startup Repair and then wait until the process is completed.

Option 5 – Try to reset the BIOS or the UEFI Settings

If updating the BIOS didn’t help in fixing the error, you can try to reset the BIOS instead.
  • Start your computer and tap the F10 key during the booting process to enter the BIOS. If it does not work, you can try tapping the F1 or F2 key as well as the Del key.
  • Once you’re already in the BIOS, tap the F9 key to get the prompt to RestoreLoad default configuration now for the BIOS.
  • Next, click on Yes and then follow the next on-screen instructions that appear to set the BIOS back to its default settings.
  • Once you’re done restoring the default settings of the BIOS, restart your computer and then check if it now boots properly.

Option 6 – Try to physically check the hardware

You should also check the physical status of the hardware in your computer. You can clean the dust off the hardware components like the Network Card of the computer. You might want to use a small blower or you could also use a soft cloth and run the components gently. Make sure that you don’t damage any parts with moisture or cause harm to any circuits while you carry out this task.
Read More
How to Fix Failed to load DLL file Error
If your operating system cannot or is not able to load a required DLL file on your Windows startup and you encounter a message saying, “Failed to load DLL”, then you’ve come to the right place as this post will guide you in fixing this problem. When you encounter this kind of issue, you will see either of the following error messages on your screen:
“The dynamic library dll failed to load.” “Failed to load dll library.”
This kind of error can occur when your Windows operating system fails to locate the DLL library which the system needs to access during startup. It can also occur when the DLL file is not in a directory specified in the path or when the DLL file is corrupted or has gone missing. Moreover, you can also encounter this error if the DLL file is infected with some malware. Whatever the case is, here are some suggestions you have to check out to resolve the problem.

Option 1 – Try to reinstall the program

The first thing you can do is to reinstall the program that’s giving you this error. Once you’ve uninstalled the program, download its latest setup file from its official site and then install it again.

Option 2 – Try checking the startup programs

You might also want to check the startup programs on your computer, especially the Windows Registry startup paths, and then remove the startup entry to the concerned DLL file.

Option 3 – Try to re-register the problematic DLL file

You may have to re-register the ntdll.dll file using the regsvr32.exe before you can successfully install the program and fix the ntdll.dll file crash error. The Regsvr32 tool is a command-line utility that can be used to register and unregister OLE controls like DLL and ActiveX (OCX) control in the Windows operating system. Follow the steps below to use it.
  • Open Command Prompt as admin from the WinX menu.
  • Next, type the following commands in the elevated Command Prompt and hit Enter to execute the command. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.
    • exe /[DLL file]
    • exe [DLL file]
Note: Replace “[DLL file]” with the name of the DLL file that was pointed out in the error.
  • After you execute the given commands, you should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. After that, try to install the program again and see if it now works.

Option 4 – Try to replace the DLL file with a trusted source

  • First, you need to get the new DLL file from another computer with preferably the same file version number.
  • After that, you need to boot your PC into Safe Mode and navigate to the paths listed below and then replace the file using a USB drive or other external storage devices.
    • x86: This PC > C:/Windows/System32
    • x64: This PC > C:/Windows/SysWOW64
  • Next, type “cmd” in the Cortana search box and right-click on Command Prompt, and select “Run as administrator” to open it with administrator privileges.
  • Now type the “regsvr32 ntdll.dll” command and hit Enter.
  • Restart your PC and check if the error is now fixed.

Option 5 – Try checking the details in the Event Viewer

Checking the details in the Event Viewer can also help you find out the root cause of the problem as the Event Viewer usually contains detailed information about the error.

Option 6 – Try running the DISM tool

You might want to repair potentially corrupted files in your system as having them could also trigger the “Failed to load DLL” error. To repair these corrupted system files, you can run the DISM commands:
  • Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
  • After that, input each one of the commands listed below sequentially to execute them:
    • Dism /Online /Cleanup-Image /CheckHealth
    • Dism /Online /Cleanup-Image /ScanHealth
    • Dism /Online /Cleanup-Image /RestoreHealth
  • Once you’ve executed the commands given above, restart your computer and check if the “Failed to load DLL” error is now fixed.

Option 7 – Try scanning your computer using Windows Defender

The DLL file might also be infected with malware or virus and to eliminate it which could explain why you’re getting the “Failed to load DLL” error. Thus, you have to scan your computer using security programs like Windows Defender.
  • Tap the Win + I keys to open Update & Security.
  • Then click on the Windows Security option and open Windows Defender Security Center.
  • Next, click on Virus & threat protection > Run a new advanced scan.
  • Now make sure that Full Scan is selected from the menu and then click the Scan Now button to get started.
Read More
Repairing or rebuilding the WMI Repository
There are times when the WMI Repository gets corrupted which results in the Provider Load Failure. To resolve this issue, you need to repair or rebuild the WMI Repository in your Windows 10 computer. In this post, you will be guided on how exactly you can do that. In case you don’t know, the WMI which stands for Windows Management Instrumentation is a set of specifications from Microsoft to consolidate the management of devices and applications in a network. The WMI is a database that stores meta-information and definitions for WMI classes. Using only these, the conditions of the systems can be known. You can find the WMI Repository in %windir%System32WbemRepository. It provides end-users with the status of the local or remote computer system. Keep in mind that you must not use this on the Server 2012 Cluster machine. Although there are command-line tools that can fix or restore the Windows Management Instrumentation repository. However, Microsoft suggests that it’s better if you verify if there is corruption. Here are a list of errors as well as permission issues you might encounter:
  • Unable to connect to root default or rootcimv2 namespaces. It fails with the error code “0x80041002” pointing to “WBEM_E_NOT_FOUND.”
  • 0x80041010 WBEM_E_INVALID_CLASS
  • When you open Computer Management and Right Click on Computer Management (Local) and select Properties, you get the following error: “ WMI: Not Found” or it hangs trying to connect
  • Trying to use wbemtest , and it hangs
  • Schemas/Objects missing
  • Strange connection/operation errors (0x8007054e)
To verify if there is corruption, you can try running the following command in an elevated Command Prompt:
winmgmt /verifyrepository
 After you enter the command, if there is a response saying, “repository is not consistent”, then the repository has an issue. If not, then something else is causing the problem. Since you are certain that corruption exists in the WMI repository, then here are some suggestions you need to check out to repair or rebuild the WMI repository.

Option 1 – Try to reset WMI Repository

  • Type “command prompt” in the Start Search and right-click on Command Prompt from the search results and then select “Run as administrator”.
  • After opening Command Prompt with admin privileges, type and enter this command: winmmgmt /salvagerepository
The command you entered is used when the winmmgmt command performs a consistency check. So if an inconsistency is detected, it will rebuild the repository.
  • Next, execute this command to see if the WMI repository now comes back as consistent: winmgmt /verifyrepository
This command will perform a consistency check on the WMI repository.
  • If it states that the WMI repository is not consistent, then you need to type and enter this command: winmgmt /resetrepository
This command is used to reset the repository to its initial state when the operating system was first installed.

Option 2 – Try to force recover the WMI Repository

The WMI Repository comes with a built-in self-recovery process so when the WMI service restarts or detects any corruption, it will automatically trigger the self-recovery procedure. This can happen in two ways:
  • AutoRestore: This will use the backup images if the Volume Shadow copy or VSS backup is turned on.
  • AutoRecovery: The rebuilding process will generate fresh images of the WMI repository based on the registered MOFs. The MOFs are available in the registry located at HKLMSoftwareMicrosoftWBEMCIMOM: Autorecover MOFs
Note: Autorecover MOFs is a key so double click on it to check its value. On the other hand, if the self-recovery procedure does not work, you can try to use the force-recovery process instead. How? Refer to these steps:
  • First, you need to check the reg key value is empty or not under this registry path: HKLMSoftwareMicrosoftWBEMCIMOMAutorecover MOFs
  • If the reg key value is empty, you have to copy-paste the reg key value from another computer. Just make sure that it’s from the System which is equivalent to the computer in question.
  • Next, type and enter this command: Winmgmt /resetrepository
  • After you enter the command, if you get an error that says, “WMI repository reset failed. Error code:0x8007041B. Facility: Win32”, then you have to stop all the Dependency Services on the WMI service by running the following commands:
    • net stop winmgmt /y
    • Winmgmt /resetrepository
This should fix the problem.
Read More
Edge DevTools An error occurred while ...
In case you don’t know, Microsoft Edge, the new default browser of Windows 10, is equipped with the essential tools that are needed to help web developers in testing their websites in the Edge browser. However, it is not without its flaws as there are instances when you could also encounter some errors when using DevTools. One of these errors is the “An error occurred while starting the profiling session” error. You can see this error message in the DevTools Memory Panel, worry not for this post will help you resolve it. A memory panel is one that primarily measures your memory resource usage and compares heap snapshots in different states of code execution. The Memory panel also provides profiling of three different types, such:
  • Head Snapshot
  • Record Allocation timeline
  • Record Allocation profiles
Using a memory panel, you can find issues that affect the page performance in the most common scenarios like bloats and memory leaks. There are two steps you need to carry out to fix this error that’s associated with the Memory Panel of Microsoft Edge (Chromium) DevTools. First, you need to access the Microsoft (R) Diagnostics Hub Standard Collector Service. Second, you need to restart this service. For detailed steps, follow the instructions provided below. Step 1: Access the Microsoft (R) Diagnostic Standard Collector Service To access the Microsoft (R) Diagnostic Standard Collector Service, follow these steps:
  • Tap the Win + R keys to open the Run dialog box.
  • Then type “services.msc” in the field and hit Enter or click OK.
  • This will open the Services Manager. Here, look for the Microsoft (R) Diagnostic Service from the Services panel that opens on the right-hand side.
Step 2: Now restart the Microsoft (R) Diagnostic Hub Standard Collector Service
  • After accessing the Microsoft (R) Diagnostic Standard Collector Service, right-click on it and select the Restart option.
  • Once it’s done, exit the Microsoft Edge Developer Tools as well as the tab.
  • Next, open a new tab and navigate to your page and tap the F12 key.
  • Now, try to check if profiling begins.
Read More
Installing Windows 11 on Raspberry Pi 4
A lot of controversies and mixed emotions have come from statements about Windows 11 minimum system requirements, especially ones linked to TPM. Naturally, each time some software company giant announces how things are must have there are people who go out and prove them wrong. This time Raspberry Pi community was one which demonstrated that not only Raspberry Pi does not have a TPM module, it can run the full desktop version of Windows 11

Windows 11 on Raspberry Pi 4Raspberry Pi 4 and things you need for Windows 11 installation

In order to actually install Windows 11 on your Pi, there are certain things that you will need. Check out the below list and prepare everything.
  • Raspberry Pi 4 4GB or 8GB
  • A 32GB or larger SSD via a USB 3 caddy. Best for performance or 16GB or larger microSD card
  • USB boot enabled, see below.
  • A micro SD card with the latest Raspberry Pi OS
  • Windows 10 PC
  • USB to Ethernet or WiFi dongle
  • Bluetooth dongle (if you want Bluetooth)
  • Keyboard, mouse, HDMI, and power for your Raspberry Pi

Configuring Pi to boot from SSD

In order to boot from SSD be sure that firmware and bootloader are up to date on the latest version and upgrade if needed. Be aware that this firmware update can only be performed using the official Raspberry Pi OS. Also if you are eager and want to use a standard microSSD card instead of an SSD to run Windows 11 feel free to skip this entire section.
  1. Boot from microSSD with the latest Raspberry Pi OS on it.
  2. Update firmware and OS using the terminal by typing sudo apt update sudo apt full-upgrade sudo rpi-update
  3. Reboot your Pi
  4. Install the latest version of bootloader again using the terminal with the command sudo rpi-eeprom-update -d – a
  5. Reboot Pi
  6. Launch raspi-config on your Pi via terminal with sudo raspi-config
  7. Select option 3 (Boot options – Configure options for start-up) from boot options
  8. Select Boot ROM version and press ENTER
  9. Select latest and then OK
  10. Select NO when prompted to reset boot ROM to defaults on the latest version boot ROM selected screen. Press OK
  11. Select Boot order and press ENTER
  12. Select USB Boot and click on OK and remove microSD card from Pi
  13. Select Finish and click on NO when prompted to reboot

Creating Windows 11 installation image for Pi 4

In order to install Windows 11 on our Pi, we must create an installation image, follow the steps below explaining the process.
  1. Go to https://uupdump.net/
  2. Search for Windows 11 Arm
  3. Select the latest build for arm64
  4. Select Language on which you would like installer and Windows
  5. Pick Windows edition you would like
  6. Set download method to Download and convert to ISO and click on Create download package
  7. Extract downloaded content into win11 folder and go into it
  8. Double click on uup_download_windows.cmd
  9. On the security warning screen click on More info and then on Run anyway
  10. Wait for the process to finish completely
  11. Once the process is finished, press 0 to close the prompt

Installing image on microSSD or SSD

If previous steps of instruction were follower precisely you now have an ISO image that can be installed onto microSSD or SSD
  1. Connect SSD or insert microSSD card into your PC
  2. Go to https://www.worproject.ml/downloads
  3. Download Windows on Raspberry imager and extract it into the win11 folder
  4. Open Imager and allow it to make changes to your computer, set your language, and click on next
  5. Select storage drive where you would like to install Windows
  6. Set device type and click on next
  7. Select our Windows 11 ISO image we created and click on next
  8. On the drivers screen select Use the latest driver package available on the server
  9. On UEFI firmware select screen choose Use the latest firmware available on the server
  10. On configuration screen click on next
  11. Check your setting on the installation overview and if everything is ok click on install
  12. Wait for the whole process to be finished
  13. Once the process is completed, close Windows on Raspberry imager, take out SSD or microSSD card from PC and connect it on your Pi along with Pi peripherals.

Setting Windows 11 on Pi

In order to actually use Windows 11 on our Raspberry Pi we now have to set up the Windows 11 install using the standard post-installation setup sequence.
  1. Power up Pi and press ESC when prompted
  2. Go to Device manager and press ENTER
  3. Select Raspberry Pi Configuration
  4. Select Advanced configuration
  5. Set Limit RAM to 3GB to a disabled state, press F10 to save, and ESC to exit.
  6. Select Display configuration
  7. Set the resolution to desired option and press ENTER, F10 to save, and ESC to exit
  8. Go to CPU configuration
  9. Check if the CPU clock is set to default, if not set it
  10. Press ESC to go back all the way to the main menu
  11. Select Continue to exit BIOS and boot your Raspberry Pi with Windows 11 on it
And there you have it, fully working Windows 11 OS on Raspberry Pi despite what Microsoft says Note that due to lack of some drivers performance can be less than optimal, for example, full HD videos will not work since there are no compatible graphic drivers for Pi and some other stuff like Wi-Fi will also cause some issues but overall Windows 11 is working pretty well.
Read More
1 2 3 171
Logo
Copyright © 2023, ErrorTools. All Rights Reserved
Trademark: Microsoft Windows logos are registered trademarks of Microsoft. Disclaimer: ErrorTools.com is not affiliated with Microsoft, nor claims direct affiliation.
The information on this page is provided for information purposes only.
DMCA.com Protection Status