Fix: Windows 10 Won’t Boot
Windows 10 boot process is very simple. Whenever you start your computer, the UFEI or BIOS firmware is loaded. These perform a short series of steps on your hardware called Power on Self Test (POST). After performing the test and if no errors were found, the BIOS scans the master boot record, which in turn loads an essential file to your RAM (the file is called Winload.exe). After the file is loaded, it kicks off the startup process by loaded NTOSKRNL.EXE and HAL (NT Kernel is the heart of Windows and HAL stands for Hardware Abstraction Layer).
If you are unable to boot your Windows, it probably means that your computer is unable to load Winload.exe. This is probably not a good thing and not always can you get your operating system back on track. What we can do is enter the Recovery Environment (RE), and try checking if the boot files are corrupt. If they are, we can try fixing them using the command prompt. Furthermore, we can also check if there is any problem with your hard drive.
Solution 1: Repairing Corrupt Boot files
The first and foremost thing you should check if you are having problems booting your computer is your boot files. Boot files usually get corrupt after a potential Windows update. If the update was complete halfway or it got stuck, there are chances that your boot files have become corrupt. We need to run the chkdsk command to fix any discrepancies. We will be running the command prompt in RE and try doing all the operations from there. Windows cannot repair itself because the boot parameter is corrupt. No recovery will fix it for some reason even though the recovery tools are present.
- Restart your computer and upon booting, press F11 to go into the recovery environment. Now select Troubleshoot.
- Click on Advanced from the list of options available and select command prompt.
- Once at the command prompt, execute the following command. If you have Windows installed to some other directory, you can replace “c” with the name of the drive.
If check disk utility only scans your computer and doesn’t perform any fixes, you need to execute the following command:
System file checker (SFC) is a utility in Windows which allows users to scan and restore corruptions present in their operating system. It is integrated with Windows resource protection, which protects folders, registry keys, and critical system files as well.
- Wait for the process to complete and do not cancel at any stage. After all the operations are performed, restart your computer and see if you can boot as expected.
Solution 2: Using Bootrec (bootrec.exe)
Bootrec is tool provided by Microsoft in Windows recovery environment (also called Windows RE). When your computer fails to boot successfully, Windows automatically starts in RE. This environment has several tools that can potentially fix your computer such as Command Prompt, Startup Repair etc. We will try using Bootrec using the command prompt and see if this fixes the problem for us.
- Restart your computer. When your computer loads up (when Windows logo appears), press F8 or F11.
- Navigate to the command prompt like we did in the first solution.
bootrec /fixmbr
How to Fix Startup Repair in Windows 10 | System Reserved
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
Each command should give you a confirmation that the operation completed successfully. Now reboot your system and hopefully, the problem will be solved.
Solution 3: Disabling Network Drivers
A recent update to the Windows operating system in early 2018 broke many network drivers in many devices across the globe. The reason why this happened is unknown. The users faced the same problem under discussion that they were unable to boot their operating system successfully. What you can do to solve this problem is to boot your computer in safe mode and disable ALL the network drivers. When you have successfully booted up, you can revert the drivers to a previous version.
- Boot your computer in Windows 10 Safe Mode Command Prompt.
- Once in Safe Mode, press Windows R, type “devmgmt.msc” in the dialogue box and press Enter.
- Expand the category of Network adapters, right-click on each network adapter one by one and select Disable.
- Once you have disabled all the network drivers on your computer, boot your computer out of safe mode and attempt booting in the normal way.
- After you have booted normally, navigate to the device manager, right-click on the adapter and select Properties. Here you will see an option to Roll-back driver. If you don’t, you can download the older driver from the internet and store it in an accessible location on your computer. Then you can click Update, and after choosing to update manually, choose the driver to install.
Note: If you already know which software caused this mess, you can boot into Safe Mode, uninstall/disable the software and then try booting the normal way.
Solution 4: Using Command Prompt to Restore
If all the above solutions don’t work as expected, you use the command prompt to restore your Windows. We will first backup some files and then proceed. We have listed down each step comprehensively. Make sure you follow each and every step and do not even skip a single one as it can render the PC unusable.
- If Windows is stuck in an infinite boot loop after an update fails to install, cut the power of the computer by pulling the plug. If you own a laptop, remove the battery. If you are using a laptop where you cannot remove the battery, holding the power button for 5 seconds should turn off the computer instantly.
- After you start your computer again, you should an automatic repair dialogue. If you don’t, close your computer like mentioned above again and the third time, you will see it. Now navigate to the command prompt as explained earlier in the article.
- Once in the command prompt, type “c:” We are doing this to check where your Windows is installed. Type “dir” to list all the contents. If you see Program files in the result, it means that Windows was installed here. If it wasn’t, type some other drive’s name such as “d:” As you can see in the example below, the installation files are present in drive ‘D’.
If you have already used this solution before, make sure you use another name instead of ‘backup’ such as ‘backup1’.
Make sure that you use the same name which you initialized in step 4. In this case, we are using the name ‘backup’.
You will see a bunch of items with numbers before them. If you don’t see numbers and there is a string of zeroes, you cannot continue with this solution. Instead, you have to use System Restore.
The above command has copy following with (star dot star), then a space and then (dot dot).
When prompted, type “A” to indicate All.
- Now Windows will reboot. Do note that the booting might take quite a while depending on how many files were operated. Let it complete and do not cancel at any step. Hopefully, after a while, you will be able to log into your computer once again without any problems.
Note: Do note that this method might render a ‘few’ features of Windows. This is very rare but if it happens, you can always search our forums for fixes. The problems are mostly very minute, nothing of critical nature.
Solution 5: Backing up your Data and doing a System Restore
If you cannot restore your computer manually in the solutions mentioned above, you will have to back up your data manually in RE and then do a system restore. Do note that the backup we do will not be automatic and you will an external hard drive or USB to copy the files into.
- Open the command prompt in RE as mentioned in the article earlier. Once at the command prompt, execute the instruction ‘notepad’. This will launch the normal notepad application on your computer in RE environment.
- Press File Open in the notepad. Now select ‘All Files’ from the option “Files of type”. You will now be able to see all the files on your computer using this explorer.
- Now navigate to My Computer again, locate the removable hard drive and paste all the contents in it. Repeat the steps until you have successfully backed up all your important data in the external hard drive or USB.
Once you have backup up your data, you can start doing a system restore on your computer. For you to perform a system restore, you must have a restore point configured already. Normally, Windows automatically creates a restore point when there is an update or when you install a new feature.
- Navigate to the Advanced options as mentioned earlier in the article. Click the option “System Restore”.
- Select the restore point from the list of options and perform a system restore. Do note that you might lose some data which was entered in the computer after the restore point was created.
Note: As you can see, there is also an option to Go back to the previous version of the update. If you know with certainty that an update broke Windows, you can try going back to the previous version and see if this does the trick for you.
Last Resort: Installing Fresh copy of Windows
If you are not able to boot your computer normally using the steps mentioned, you need to install a fresh copy of Windows on your computer. There is still a way you can keep your information intact.
For Windows to install, it needs a drive where you will be installing the installation files. You can either install Windows on a separate drive when the options comes. This way the old drive will still have the data and if it is accessible later on, you will be able to copy it to the new drive and format it accordingly. You can check out our detailed article on how to install Windows 10.
Tip:
You can enter the recovery environment by inserting a USB or Disk with Windows installation media and selecting “Repair this computer”. This can be used when you are unable to enter RE in the steps above.
How to Fix the MBR (Master Boot Record) in Windows 10
The MBR (Master Boot Record) is a set of information in the very first sector of your bootable system hard drive. It tells the computer where it can find the operating system (or systems) and load it in the memory. If something goes wrong with the MBR, you may not be able to boot normally. If you’ve got a busted MBR, here are the most effective ways to fix the MBR.
How Does the MBT Become Damaged or Corrupted?
Although the MBR is a special region of the hard drive, it’s not fundamentally different from any other data on the disk. This means that it’s also susceptible to the same threats. Sudden power loss could corrupt any area of a drive, especially if it was in the process of writing to that area. Malware such as viruses can also deliberately alter your MBR to achieve its individual malicious goals.
Whatever the reason for your MBR’s demise, there are several ways to repair it.
Use Automatic Repair
Windows 10 is a Smart operating system, and it’s much better at fixing its problems than previous versions. At startup, assuming your MBR isn’t completely in ruins, Windows will detect that there’s something amiss.
You’ll get a message that says, “Your PC did not start correctly,” and you’ll see options to either restart the computer again or to select “Advanced options.”
Under Advanced options, you’ll find Troubleshoot Startup Repair.
Follow any prompts and wait for the process to finish. This may take a very long time since Windows builds the MBR by scanning the entire hard drive. However, at the end of the process, things should work as normal again.
Use the Command Prompt to Fix the MBR
You can use the Command Prompt in Windows to manually initiate an MBR repair. If you encounter the Automatic repair screen when you start up Windows and you’d prefer to use the Command Prompt, choose Advanced Options Troubleshoot Command Prompt instead.
Once you’re at the Command Prompt, you can use a tool called Bootrec (Boot Recovery) to fix the MBR.
First, type BOOTREC /FIXMBR and press Enter. After a little while, you should see the message “The operation completed successfully.”
Congratulations, you’ve repaired the MBR, but your computer may still refuse to boot correctly if you restarted the system now.
So, just to be safe, type BOOTREC /FIXBOOT and press Enter.
After receiving the same confirmation message as above, you can restart the computer to see if things are back to the way they should be.
Use a Bootable Windows Disk to Fix the MBR
What if your MBR is so busted that you can’t even get Windows 10 to show you the Automatic repair option at startup? There are only a few options open left if this is the case.
If you just want a fresh start and don’t have any critical information to back up, the fastest solution is to wipe your boot drive and reinstall Windows. This is something we especially recommend if a corrupted MBR is only part of your overall problems. If you’ve been struggling with multiple bugs and issues in Windows leading up to MBR corruption, strongly consider replacing it all and solving multiple issues in one fell swoop.
Solved: Windows 10 Won’t Boot (100% Working Solution)
If, as far as you know, the only issue is a corrupted MBR, then you can use bootable Windows 10 installation media to access the repair function as well. Simply boot from the Windows 10 installation media and, instead of choosing “Install” choose to repair your computer instead.
Once you select repair, you’ll have the same Troubleshoot option as detailed above. You can also choose Command Prompt under Troubleshoot Advanced Options and then use the same instructions to fix the MBR via the Command Prompt mentioned above.
If you don’t have suitable, bootable Windows 10 media and want to know how to create it yourself, have a look at How to Create a Windows 10 Bootable USB Recovery Drive.
If the MBR Is Corrupted Repeatedly
If you’re facing repeated corruption issues with your MBR, you’ll need to start looking for a culprit. If you’re using a mechanical drive, MBR corruption can be the result of improper power cycling. If your computer has turned off every time you’ve come back to it you may want to consider buying an Uninterruptible Power Supply (UPS) to counter poor electricity services.
Repeated MBR corruption can also be the result of a failing hard drive. That’s especially true of mechanical hard drives, which are more prone to failure than modern solid-state drives (SSDs). If you suspect your hard drive might be at fault, read How to Check Your Hard Drive for Errors for practical advice on how to make sure things are still good to go. If your hard drive is failing, make a backup of your most essential data and perhaps take this as an opportunity to upgrade to an SSD.
If it’s not the hard drive nor the power company that’s to blame, a faulty power supply unit (PSU) could also be behind the computer suddenly switching off. An overheating CPU that triggers the protection failsafe will instantly kill the power and happens when your cooling solution is no longer working properly.
Preventing MBR Corruption
Except for physical drive failure, you can largely prevent the other causes of MBR. Ensure you have virus protection, practice basic safety when running software from unknown sources, and shut down your computer properly instead of cutting the power.
As mentioned above, you can also ensure that your computer doesn’t suffer a power cut by using a UPS to give it time to switch off properly if the power does go out.
How to repair Windows 10 (and 11) in 4 steps
Sometimes a Windows 10 system starts misbehaving to the point where repair is needed. This often takes the form of worsening performance or stability, and can originate from damage to, loss of, or corruption of Windows system files typically found in the C:\Windows folder hierarchy. When that happens, users would be well advised to break out the following routine to help them set things back to rights.
I initially wrote this story in 2016, but as Windows 10 has evolved over time, some of the steps have changed a bit. I’ve now updated it for the latest versions of Windows 10. That said, most of these approaches also work with Windows 7 and 8 (with slight variations), and the advice here applies almost identically to Windows 11, which Microsoft is gradually rolling out to Windows 10 users whose hardware can support the new OS via Windows Update from October 2021 into early 2022.
The Windows 10 (or 11) repair drill
The idea is to first try the initial step in the sequence. If that doesn’t fix what’s broken, advance to the next step. Keep working through the steps in order until you reach the end, and you are bound to fix the vast majority of problems. (The only remaining step at that point would be to replace the system on which the software is running, and that’s outside the scope of this story.)
The amount of time and effort required for each step goes up incrementally. Some steps involve additional work to restore the prior state of your PC more or less back to where it was prior to taking that step. Thus, the most important bit of advice I can dispense for those who must venture beyond Step 1 is this: make a complete backup of your system to provide source for files and information that might otherwise go missing. Ignore this advice at your own risk.
Back it up before you lose it!
Any time you make major changes to a Windows system, such as installing a major application suite like Microsoft Office or performing an OS upgrade or repair, it’s a good idea to begin that process with a complete backup. The important thing is to use a backup tool that creates an image backup of your boot/system drive. That will allow you to rewrite that drive and restore your system to normal operation should anything go wrong with your changes or repairs. See my article “How to make a Windows 10 or 11 image backup” for instructions.
Step 1: Using DISM and SFC for system repair
Since I wrote the original version of this story, I’ve obtained direct advice from Microsoft that it’s best to run DISM before running the System File Checker, a.k.a. SFC. Hence, I am reversing the order of events for this step. I’ll Echo Microsoft and say “Always run DISM first, then SFC second, not vice versa.”
DISM is the Deployment Image Servicing and Management tool. It’s a kind of Swiss Army knife for working with Windows operating system images, both offline and online. DISM can often fix things that SFC can detect but that it cannot itself fix. DISM supports a raft of capabilities with switches and parameters to match, but basic system file repair syntax is reasonably easy (though it often requires multiple passes before it can set things straight).
You must run DISM in an Administrator: Command Prompt window (press the Windows key X combination and select Command Prompt (Admin) from the resulting pop-up menu) or in an Administrative PowerShell or Windows Terminal session. Here’s some sample syntax (consult the TechNet DISM Technical Reference for all the gory details):
dism /online /cleanup-image /checkhealth
Most of the time when you run this command, the output will find nothing amiss, as shown in Figure 1:
The /checkhealth command simply checks the running image (that’s what /online tells it to do) to see if it can detect any damage or corruption. Because it’s only checking file hashes and signatures, this command completes in under one minute on most machines. The good thing about /checkhealth is that it not only tells you if it finds damage but if that damage is repairable or non-repairable. If it’s repairable, you can proceed to the /restorehealth option (covered in the following paragraphs); if it’s non-repairable, jump to Step 2.
If DISM reports that component store corruption is found and is repairable, you should attempt repairs. That syntax reads:
dism /online /cleanup-image /restorehealth
Even if errors were detected in the preceding step, this command should complete successfully. It replaces corrupt or questionable elements in the Windows Side-by-Side (WinSxS) store, reading from a local copy of your Windows image files.
The /restorehealth command can be tricky to use. Because it can actually repair a Windows image, it needs source from which to attempt such repairs. You can omit the /source option, but if you do, the command will try to grab its files from Windows Update over the internet. This may or may not work, depending on firewall settings on your network.
A safer bet is to point DISM at a known good source for Windows image components on the local machine (or on your local network). This can be a Windows image (.wim ) file or a compressed Windows image (.esd. which is used for electronic software downloads of Windows installations, as the file extension is meant to communicate). You can also point to a separate copy of a WinSXS folder (the usual directory path is C:\Windows\WinSXS ) taken from another PC with similar or identical hardware for which dism. /checkhealth returns a clean bill of health.
The syntax for image files is where things can get interesting. To point to the install.wim file that shows up in ISO downloads for the Windows 10 installer on a USB flash drive designated L:. for example, you must use the following source specification (which uses the first image it finds inside the.wim file, designated :1 ):
To use an ESD file, change the wim items to esd, as shown here:
If you run into difficulties getting this to work, try adding the /limitaccess switch to your command strings. This stops DISM from attempting to grab source files from Windows Update, which it will sometimes do even if pointed at a local source. If you just can’t get either of these to work, try a WinSXS folder instead.
Note: the version and language for the /source image must be identical to that for the image to be repaired. This may mean using HeiDoc.net, UUP Dump, or Microsoft’s Media Creation Tool to grab the correct Windows 10 or 11 version/build (see my article “The best places to find Windows 10 ISOs” for details on how to use these sources) and creating media or mounting the ISO file to give DISM the right /source from which to work. For Windows 11, check the Windows Insider Preview Downloads page to grab the proper ISO.
Figure 2 shows typical DISM output using /restorehealth :
Next, it’s time to run SFC, Microsoft’s System File Checker. To quote TechNet, the system file checker “scans and verifies versions of all protected system files.” It can tell you if it finds anything amiss if you enter SFC /scannow at the command line.
As with DISM, you must run SFC from an Administrator: Command Prompt or an Administrative PowerShell or Windows Terminal session. This command takes 5 to 10 minutes to complete, depending on your PC hardware. Unlike DISM, SFC scans and initiates repairs within a single command.
Figure 3 shows sample output when SFC finds files in need of repair. If this occurs on your PC, repeat the /scannow command until it gives the clear bill of health shown in Figure 4.
In my experience, 80% of all problems will be solved at this point, so the odds are in your favor that you won’t have to keep going. But if DISM can’t fix your Windows image, or SFC can’t or won’t make repairs to your system files, proceed to Step 2.
Step 2: Try a recent restore point or image backup
A restore point is a snapshot of a Windows PC’s OS state from a specific point in time. If enabled, the Windows System Restore capability can create and maintain restore points on your behalf. To see if this is an option on your target machine, type restore point into the Windows 10 search box. The System Properties window should open to the System Protection tab, shown in Figure 5.
To look at restore points, you must work through the System Restore wizard. Click the System Restore. button to launch the wizard, then click the Next button on the first pane of the wizard to see a list of restore points available to you. (If you don’t like what you see, or you don’t see something from before your troubles started on this machine, click the Show more restore points checkbox for a complete list of what’s available to you.) Click the restore point to which you would like to revert.
Figure 6 shows the lone restore point available on my test PC.
Because I have only one restore point — I don’t use them much any more, for reasons I’ll explain coming up — I picked that item to show you what appears when you select a restore point in this utility. If you click the Scan for affected programs button it will tell you if any programs or drivers will be affected by rolling back to the restore point you’ve selected. In this case, there’s no impact, as shown in Figure 7. If something were to be affected, it would show up in either the top or bottom list in that results pane.
It usually takes between 5 and 15 minutes to revert to a restore point. The amount of additional effort to catch back up to where you left off depends on the number of items that need to be installed or updated, as shown in Figure 7. This can take from minutes to an hour or more depending on size and scope.
All this said, I don’t use Restore Points anymore. I’ve run into occasional issues with failed restores, and I’ve seen plenty of discussion in Microsoft Community and TenForums among other users who’ve had similar problems. My preference is to restore an image built using Macrium Reflect (free or commercial; I use both). It’s faster than System Restore, and I’ve never been unable to restore a valid, integrity-checked Reflect backup. You decide what’s best for you; I use Reflect.
Restoring an image backup is much like reverting to a restore point: choose the image (usually by date and time) to which you’d like to roll back, then initiate the restore procedure. For example, Macrium Reflect offers a “Restore” menu, then allows you to browse stored backup files to pick the one you want in an Explorer-based Open window.
If reverting to a restore point or image backup doesn’t work (or you don’t have either of these), it’s time to move on to Step 3.
Windows 10/11 Startup Repair Not Working? Solved Now!
When you encounter Windows 10/11 Startup Repair not working problems, you can refer to this article and find effective solutions here.
By Lily / Last update April 20, 2023
Overview of Startup Repair not working in Windows 10/11
Windows 10/11 has its own repair tools, and Startup Repair is a frequently used one among them. You can use it to scan and repair some PC issues like corrupted system files or invalid boot files. That is, if your Windows 10/11 won’t boot, you can use installation disc or system repair disc to boot into Advanced options, and then perform a Startup Repair.
However, some users find Windows 10/11 Startup Repair not working sometimes. Here are 2 most common cases:
Case 1: Windows 10/11 Startup Repair loop
Windows 10/11 Startup Repair loop is also known as Windows 10/11 Startup Repair stuck. When you encounter this error, Windows 10/11 will boot again and again into Startup Repair and present an endless loop, so that you cannot access anything else on the computer.
Case 2: Windows 10/11 Automatic Repair failed
Startup Repair is supposed to help you to fix some issues, but it will not always work. Sometimes, you may receive a message on the screen that says Windows 10/11 Automatic Repair couldn’t repair your PC.
Learn how to resolve Startup Repair not working in Windows 10/11 under the two cases separately. You can also get a bonus tip for system protection.
Case 1: Windows 10/11 Startup Repair loop
If you cannot use Startup Repair, then your option is to disable automatic restart, run chkdsk and rebuild bcd settings.
Solution 1: Disable automatic restart
To disable automatic restart, please follow the steps below:
Restart your computer and then on the screen titled “Choose an option”, click Troubleshoot Advanced options Startup Settings Restart subsequently.
On the Startup Settings screen, press 9 or F9 to choose Disable automatic restart after failure. After that, just wait for your PC to boot and see if Windows 10/11 Startup Repair loop is solved.
Solution 2: Run chkdsk
Corrupted boot partition may cause Windows 10/11 Startup Repair loop issue. You can try to check the boot volume using chkdsk:
Restart your computer and then on the screen titled “Choose an option”, click Troubleshoot Advanced options Command Prompt.
In the Command Prompt window, type chkdsk C: / f /r and press Enter to check your system partition for corrupted, invalid or deleted system files.
Solution 3: Rebuild bcd settings
To rebuild bcd settings, you may follow the instructions below:
Open Command Prompt as mentioned in Solution 2.
Type following command lines and press Enter after each to fix Startup Repair stuck issue:
Case 2: Windows 10/11 Automatic Repair failed
If you are told Windows 10/11 Automatic Repair couldn’t repair your PC, then try the following solutions:
Solution 1. Run sfc /scannow command
You can run the sfc /scannow command (System File Checker) to repair system files.
Restart your computer. Open Command Prompt in Advanced option as mentioned above.
When Command Prompt appears, type bcdedit and press Enter to locate the drive where Windows is installed.
Type sfc /scannow /offbootdir=d:\ /offwindir=d:\Windows and press Enter to repair the corrupted files. Remember to replace “d:” with your Windows drive letter.
Restart your computer after the process is done.
Solution 2. Disable early launch anti-malware protection
If you have been facing the problem after installing an anti-malware program, you can disable anti-malware protection to fix Windows 10/11 Automatic Repair failed.
Restart your computer. On the screen titled “Choose an option”, click Troubleshoot Advanced options Startup Settings Restart.
Press 8 or F8 to select Disable early launch anti-malware protection at the list.
Extra tip for fixing Windows 10/11 startup repair issue
As you see, the Windows 10/11 Startup Repair not working problem can be caused by corrupted, invalid or deleted system files. Therefore, it’s important for you to create a system image backup so that you can restore system to a normal state when problems occur.
Here I’d like to recommend the best free backup and restore software. AOMEI Backupper Standard. It can be used in Windows Visa/XP/7/8/8.1/10/11. It allows you to create not only system backup but also disk backup, partition backup and file backup. Click the button below to download this freeware:
With the intuitive interface, you can create a system image backup via AOMEI Backupper in only three steps: click Backup and System Backup select a destination path to save the backup image click Start Backup.
- If you want to continuously protect your computer, you can create a scheduled backup at daily, weekly, monthly, etc.
- Incremental or differential backup is recommended, because it only backs up the changed data, thus saving much time and disk space.
- To restore your computer when it fails to boot, you can create a bootable disk beforehand.
Summary
There are five solutions offered in this article to help you solve the Windows 10/11 Startup Repair not working problem. You can pick one solution according to your situation. To restore from possible system errors, you may backup your computer with AOMEI Backupper.
If you want to protect unlimited computers within your company, you can pick AOMEI Backupper Technician or Technician Plus. It allows you to create a portable version of this software and directly run off a USB flash drive without installing on a different computer.
Then, you can use this software to deploy/restore system image file to multiple client-side computers over network, migrate operating system to SSD, clone large SSD to smaller SSD etc.
Best Free Backup Software
- System and Files Backup
- Automatic Backup
- Incremental Backup
- File Synchronization
- Hard Drive Cloning
Do you need any more help?
Have you solved your problem? Otherwise, enter the query in the search box below.
