Error Code 0xc00000e9

Hello and welcome to our Reasons to Defrag Hard Drive. You ought to defrag your hard drive, in case your PC is slow. This could enhance the efficiency and pace of your PC too as its hardware longevity. It places them where there is space, whenever your PC saves files. Often files are separated into bits. For example, whenever you remember a file and focus on it, it frequently doesn't fit back in exactly the same physical place. Where it can your PC divides up the file, occasionally into several parts, and saves it.

Why defrag?

Fragmentation causes difficulties that doing a defrag can correct. Fragmented files because it requires more resources and time to locate and remember these files slow down your pc. Applications may also take longer to load. Defragging can prolong the life span of the components. A defragged hard disk too can raise your likelihood of recovering lost information. Once fragmentation starts, it can propagate fast -- demanding defragging. It's like the pages of a publication are divided and hidden in several locations around a house, if a file is fragmented. It's like the pages of the book being brought back together, should you defrag. Defragging discovers all the bits of the file and places them in contiguous, actual places.

How will you defrag?

To defrag your hard drive, you must utilize software or utility. There are lots of defragging tools available. SpeedyPC Pro, a whole package of cleaning and optimization tools, can defragment your PC. Before you defrag, it's best to assess your hard drive. This evaluation finds if a defrag is needed and how much of the disc is fragmented. You simply allow the application do the work if it's determined that you must defrag your PC to enhance performance. To be able to defrag a drive, free disk space will be required by your PC. Defragging can take a while. How long depends on several variables, such as the system resources accessible, the disc volume, the number of files, and how fragmented the files are. It's a great idea to defrag when you don't have to use your pc or it isn't doing other jobs. For example, the night could become a great time to defrag. Be certain to close out of resource-intensive applications, like your antivirus scanner, before you defrag.

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

Changes and features

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

Fixes

Taskbar:

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

Settings:

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

File Explorer:

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

Search:

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

Widgets:

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

Other:

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

Known issues in Windows 11 repaired

Start:

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

Taskbar:

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

Settings:

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

File Explorer:

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

Search:

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

Widgets:

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

Store:

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

Windows Security:

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

Localization:

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

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

In case you don’t know, when you visit a website that uses HTTPS, it also offers an SSL certificate to the browser in order to verify the website’s identity. Although it may contain lots of things inside it, one of them is the URL of the website. So if the certificate does not match the URL to what you entered, you will most likely get the “Server’s certificate does not match, ERR CERT COMMON NAME INVALID” error which indicates that the connection is not private and the site may try to steal your data but worry not, as this post will guide you in resolving this issue. To fix the ERR_CERT_COMMON_NAME_INVALID error, here are some suggestions that might help.

Option 1 – Check the website’s certificate

If you own the website where you’re getting the error, then you might have to check if the website’s certificate is installed properly and configured on the server as it could be the reason why you’re suddenly getting the error.

Option 2 – Check the Windows Host file

You can also try to cross-check the Windows Hosts file to find out if the website you are trying to open has been blocked, because if it is, then it’s no wonder why you’re getting the ERR_CERT_COMMON_NAME_INVALID error. There are instances when some third-party application modifies the file and adds some websites to the blocklists. So if the website is indeed blocked, you need to remove it from the list.

Option 3 – Use the Google Public DNS

You might want to change your DNS to Google Public DNS as it could also help you in fixing the ERR_CERT_COMMON_NAME_INVALID error in Chrome. To do so, follow the steps below.

• The first thing you have to do is right-click on the network icon in the Taskbar and select Network and Sharing Center.
• Next, click on the “Change Adapter Settings” option.
• After that, search for the network connection that you are using to connect to the internet. Note that the option might be “Wireless Connection” or “Local Area Connection”.
• Right-click on your network connection and click on Properties.
• Then select the new window to choose the “Internet Protocol 4 (TCP/IPv4)” option.
• After that, click on the Properties button and click the checkbox in the new window for the option “Use the following DNS server addresses”.
• Type in “8.8.8.8” and “8.8.4.4” and click OK and exit.

Option 4 – Run the built-in Malware Scanner and Cleanup Tool in Chrome

In case you don’t know, there is actually a built-in malware scanner and cleanup tool in Chrome that helps you get rid of any unwanted ads, pop-ups, and even malware, as well as unusual startup pages, toolbars, and other things that could affect the performance of the browser. In addition, this built-in tool in Chrome might also help in fixing the ERR_CERT_COMMON_NAME_INVALID error.

Option 5 – Reset Chrome

Resetting Chrome can also help you get rid of the error. Resetting Chrome means restoring its default settings, disabling all the extensions, add-ons, and themes. Aside from that, the content settings will be reset as well and the cookies, cache, and site data will also be deleted. To reset Chrome, here’s what you have to do:

• Open Google Chrome, then tap the Alt + F keys.
• After that, click on Settings.
• Next, scroll down until you see the Advanced option, once you see it, click on it.
• After clicking the Advanced option, go to the “Restore and clean up option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
• Now restart Google Chrome.

If you suddenly encountered an error that says, “No Audio Output Device is installed” on your Windows 10 computer, worry not for this post will guide you on how exactly you can fix the problem. There are several possible reasons why this error pops up. It could be due to a recent Windows 10 update you’ve installed, or it could be due to a corrupted or outdated audio driver, and so on. There are several potential solutions to this error. You can try running the built-in Audio Playing troubleshooter or update or uninstall the Audio driver. You could also try to update the Intel Smart Sound Technology Audio Control driver, as well as contact support for your laptop or computer. For more details, refer to each one of the provided options below.

Option 1 – Try to run the Playing Audio Troubleshooter

Since the Windows 10 operating system has the Playing Audio Troubleshooter, you can use this troubleshooter to try and fix the problem with the “No Audio Output Device is installed” error. You can access this tool in the Control Panel or in the Taskbar Search and even on the Troubleshooters page of Windows 10. Run this troubleshooter and see if it can fix the issue or not.

Option 2 – Try to update the Audio driver

If the error has something to do with software, chances are it might be related to the audio driver – it could be that the newest version of your Windows 10 does not work well with the old version of the driver. This is why you have to update your audio driver to the newest available version.

• Tap the Win + R keys to open the Run dialog box and then type in MSC and tap Enter or click OK to open the Device Manager.
• Expand the section of the Sound, video, and Game Controllers.
• And then from the drop-down menu, select the Update Driver option and follow the on-screen instructions to install the latest version of the driver.
• Then also click on the option, “Search automatically for updated driver software.
• Restart your PC after the installation.

Note: If updating the Audio driver didn’t work, you can go to the website of your PC manufacturer and look for the support section where you can download the drivers for your computer. You just need to take note of your PC’s correct model and model number so you can find the appropriate driver.

Option 3 – Try removing and reinstalling the sound card

If option 1 didn’t work, you can also try to remove and reinstall the sound card of your computer to fix the high-pitched sound coming from your computer’s speakers.

• To get started, tap on the Windows key + R to pull up the Run box.
• Next, type in “MSC” in the box to open the Device Manager.
• After opening the Device Manager, go to the “Sound, video, and game controllers” option then right-click on the sound card.
• Finally, click on Uninstall and tick the box with a label that says, “Delete the driver software for this device” and close the Device Manager.
• Restart your computer and check if the problem’s fixed or not.

Note: After you restart your computer, the system should reinstall the speaker automatically. But if it does not reinstall, you can follow the aforementioned steps again to go to the Device Manager. From there, go back to “Sound, video, and Game Controllers” and right-click on the sound card. After that, enabling the sound card and restart your computer once more. That should fix the problem.

Option 4 – Try updating the Intel Smart Sound Technology Audio Control driver

If the three options given above didn’t fix the error, you might want to try updating the Intel Smart Sound Technology Audio Control driver. To do so, follow these steps:

• Tap the Win + X keys and select the Device Manager option from the menu.
• Next, scroll down and click on the System Devices option and select the “Intel Smart Sound Technology Audio Control” option.
• Then right-click on it and select the “Update driver” option.
• After a couple of seconds, the wizard will look for an available driver and will automatically update it.
• Restart your computer and see if the error is now fixed.

If you receive an error that says, “An unspecified error occurred during System Restore (0x800700b7)” when you tried to restore your Windows 10 PC, worry not, for this post will help you resolve the problem. This kind of error typically occurs when System Restore was not completed successfully and fails instead with this error. Before you start, you must not abruptly shut down your computer and wait for the error to occur. You may receive this error due to many possible reasons. It could be caused by your antivirus program that’s not letting the process complete or corrupted system files which causes the failure or it could also be caused by an unsuccessful installation of a Windows Update. Here are some fixes you can check out if you can still boot into your computer:

Option 1 – Try to disable your antivirus program

Disabling the antivirus program or any security software installed in your computer is always a good idea you can try when the System Restore process does not go smoothly. So before you try updating your computer again, make sure to disable the antivirus or security program and then run System Restore again, don’t forget to enable the antivirus program back again.

Option 2 – Run the DISM tool

The next thing you can do is run the DISM tool. This tool is known to repair potentially corrupted files in your system as having them could also system issues like the blank dialog boxes. 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 problem is now fixed.

Option 3 – Run the System File Checker

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files that might be the cause why you’re getting the errors 0x8024a11a and 0x8024a112. To run the SFC command, follow the steps given below.

• Type “cmd” in the Start search and then right-click on the appropriate search result.
• Next, select “Run as administrator” to open Command Prompt with admin privileges.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Now restart your computer and see if the problem is fixed or not.

Option 4 – Try to run the System Restore in a Clean Boot State

If the first three given options didn’t work and the service still keeps on failing even though the service is running, you can try putting your computer in a Clean Boot State and then try to run System Restore again.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• Now try to run System Restore again and see if the process goes smoothly.

Option 5 – Run the Windows Update Troubleshooter

You might also want to run the Windows Update Troubleshooter as it could also help in fixing the problem with System Restore. 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. On the other hand, if you can’t boot into your Windows 10 computer, here are some fixes you can try instead:

Option 6 – Try running System Restore in Advanced Startup Options

If you cannot boot into your Windows 10 computer, you can try to run System Restore again in the Advanced Startup Options.

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

Option 7 – Run the SFC scan and DISM via Advanced Startup Options

Like what you did in the first given option, you can use the Advanced Startup Options to run both System File Checker and DISM. All you have to do is boot into the Advanced Startup Options and from there select Troubleshoot > Advanced Options > Command Prompt. After accessing Command Prompt, you can run the System File Checker scan first by entering the “sfc /scannow”. As for DISM, you can run the “Dism /Online /Cleanup-Image /RestoreHealth” command.

Option 8 – Try to run the Automatic Repair Utility

You might also want to use Automatic Repair in fixing the error. To do so, follow the steps below.

• You can start by creating and booting from a bootable Windows 10 USB Stick.
• After that, click on Repair your computer located in the bottom left corner when you are on the initial Windows Startup screen.
• Next, click on Troubleshoot, and then on the other screen, click the Startup Repair option.
• Now select the operating system you want to repair. Once you do that, it will start to repair your operating system. Wait until the process is completed and then check if the problem’s now fixed.

We Couldn't Install Windows Technical Preview 0x80070070 - 0x20005 -- What is it?

Some Windows users have been experiencing errors in an attempt to upgrade to Windows 10 OS. This includes the “We Couldn’t Install Windows Technical Preview 0x80070070 – 0x20005” error code. If you’re one of the many users who’ve encountered this error, you might want to check the available space on your device. Error code 0x80070070 – 0x20005 occurs when you do not have the required space to be able to install the upgrade.

Solution

Error Causes

Just like the other alternatives of error code 0x80070070 – 0x20005 such as 0x80070070 – 0x50011, 0x80070070 – 0x50012, and 0x80070070 – 0x60000, We Couldn't Install Windows Technical Preview 0x80070070 - 0x20005 is most likely caused by the following:

• Insufficient disk space in your computer
• Incomplete installation or improper deletion of applications
• The device is infected with virus or malware

Further Information and Manual Repair

In order to upgrade to Windows 10, you need to have at least 40 to 50 GB of free space in your device. Thus, you need to free up some space in order to successfully upgrade your system to Windows 10. See below for the manual methods you can employ to solve your problem.

NOTE: It would be best to seek help from an experienced technician if you are not confident enough to perform the manual methods yourself or you can alternatively make use of an automated tool.

Method One: Clean Up Your Device

1. Click Start then browse Afterwards, click on This PC.
2. Right-click on Local Disk (C:) then choose
3. Under the General tab, click on Disk Cleanup.
4. Once the Disk Cleanup window appears, check all items you want to clear down, making sure that the recycle bin is empty and clear any temp files, as well as error logs. Click OK once you’re done.
5. Repeating the same process above, clear down your system files as well to ensure that the old OS files from your previous system are taken down by clicking on Clean up system files in the Disk Cleanup window.

 Method Two: Uninstall Unused Applications

Sometimes, there are unused applications just lying around your device. This may take up your needed space from your device for a system upgrade. Uninstalling these applications can make space that will eventually elude error code 0x80070070 – 0x20005 along with its alternatives – code 0x80070070 – 0x50011, code 0x80070070 – 0x50012, and code 0x80070070 – 0x60000.

1. Open the Control Panel then select Programs and Features.
2. Check on unused applications on your device
3. Right-click on the unused application then select

 Method Three: Remove or Archive Files

If there are tons of images, media, videos, or documents that you rarely use but will still be needing in the future, you can move these files to another drive where Windows 10 will not be installed on.

If there are no secondary drives in your device, consider using a USB Drive or external hard disk. Another option you can do is making use of cloud storage programs like One Drive or Google Drive. In this way, you’ll still have access to these files even if it’s not in a physical location while making larger space in your device.

Method Four: Scan Your Device For Viruses

Most Windows users download applications or software regularly. These applications or software might come from unsafe sites where you might have accidentally downloaded a virus or malware along with the legit application or software you intended to download.

With that said, it is highly recommended to download and install in your device a reliable and powerful antivirus. Using an antivirus, you can now perform an overall scan of your device’s system. Once you’re able to detect and remove any suspected virus or malware, you’ll now be able to get rid of the error code 0x80070070 – 0x20005. After solving the issue, you can now resume upgrading to Windows 10.

Method Five: Download An Automated Tool

Can’t seem to put up with the long and technical manual repair process? You can still fix this error by downloading and installing a powerful automated tool that will surely get the job done in a jiffy!

Outlook PST Errors

Problems occur when your PST file becomes corrupted or hits the size limit. Outlook will start to display error messages. These errors include like 0x80040119, 0x80040600, and 0x8004060c.

Error Causes

You might think Outlook problems are just a minor inconvenience. You can’t access your emails and contact information, but that doesn’t actually affect computer security, right? Wrong! Outlook problems can indicate serious corruption issues within your system.

In many cases, your PST file can even be targeted specifically by a virus.

Today, many viruses are specially designed to steal personal information and then sell that information on the online black market. Since so much personal data is stored within Outlook’s PST file, this is often the first place that viruses look.

If you don’t want some hacker in a foreign country to read your emails, steal your contact information, or do all sorts of other dangerous tasks, then we advise you to fix your PST problem as soon as possible.

Other causes include hitting the 2GB memory limit on older versions of Outlook, erroneous SMTP settings, etc,.

Further Information and Manual Repair

PST errors are an incredibly annoying problem. However, thanks to powerful software like Stellar Phoenix Outlook PST Repair, it has never been easier to fix Outlook and recover all of the data inside your PST file. That means that you won’t lose contact information, calendar entries, emails, or any other information stored in Outlook.

ScanPST.exe rarely fixes problems with the PST file. Since the application is only a few megabytes in size, its effectiveness is very limited. Although Microsoft designed ScanPST.exe to be an effective solution to any PST files, it fails miserably.

Better Alternatives to Microsoft's ScanPST.Exe

Ultimately, after downloading ScanPST.exe and running it, your Microsoft Outlook will still be unable to send or receive emails. And, to make matters worse, you might also be unable to access contact data or read your old emails.

Unlike other PST repair solutions, ScanPST.exe will not recover deleted emails or other lost Outlook data. In fact, using ScanPST.exe can sometimes cause your personal data to become even more difficult to recover.

If you do want to try out ScanPST.exe, then go ahead. While it probably won’t make your PST errors worse, it won’t even come close to fixing them. If you’re ready for a more serious solution to PST problems, then keep reading.

Why are Outlook problems dangerous?

You might think Outlook problems are just a minor inconvenience. You can’t access your emails and contact information, but that doesn’t actually affect computer security, right? Wrong!

Outlook problems can indicate serious corruption issues within your system. In many cases, your PST file can even be targeted specifically by a virus.

Today, many viruses are specially designed to steal personal information and then sell that information on the online black market. Since so much personal data is stored within Outlook’s PST file, this is often the first place that viruses look.

If you don’t want some hacker in a foreign country to read your emails, steal your contact information, or do all sorts of other dangerous tasks, then we advise you to fix your PST problem as soon as possible.

How do I actually fix Microsoft Outlook PST errors?

Microsoft’s ScanPST.exe application clearly doesn’t work. So what’s the next best option? Well, a program called Stellar Phoenix Outlook PST Repair has been helping PC users solve Outlook problems for several years. As the world’s leading Outlook solution, Stellar Phoenix Outlook PST Repair will quickly and effectively repair any PST problems you encounter.

So how does Stellar Phoenix Outlook Repair work? Well, it starts by finding your PST file. Once the PST file has been found, Stellar Phoenix Outlook PST Repair determines if the file is corrupt or full. It will then repair your PST file either by removing the size limit or by fixing the corrupt files.

How Does Stellar Phoenix Outlook Repair Work?

Once Stellar Phoenix Outlook PST Repair determines that your calendar appointments, contact data, and emails have all been successfully recovered, it permanently restores access to your PST file.

In fact, Stellar Phoenix Outlook PST Repair can even restore Outlook data that you deleted a long time ago. So, instead of just being a PST error recovery tool, Stellar Phoenix Outlook PST Repair is also a powerful data recovery program.

After letting Stellar Phoenix Outlook PST Repair go to work, open up Outlook and try it out. You’ll have full access to all of your Outlook files and folders, and all of those ScanPST.exe problems will be a thing of the past.

Advantages of Stellar Phoenix Outlook PST Repair Software

Stellar Phoenix Outlook PST Repair comes with many advantages. Here are just a few reasons why it’s such a popular program:

• Easy-to-use: Don’t worry if you’re not a computer genius. Stellar Phoenix Outlook Repair is incredibly easy to use. Even if you barely know how to send an email over your computer, the program has a straightforward interface that anybody can understand. If you can click the left mouse button, then Stellar Phoenix will be easy to use.
• Goes to work instantly: It takes only seconds to download and install Stellar Phoenix Outlook PST Repair. Once you’re ready to perform a scan, the program goes to work instantly. It identifies your PST file in an incredibly short amount of time, and before long, you’ll be able to access Outlook once more.
• Effective: Unlike the infamously useless ScanPST.exe application, Stellar Phoenix Outlook PST Repair actually works like it’s supposed to. It allows users to safely recover all of their most important data. While ScanPST.exe can actually damage your PST file, Stellar Phoenix Outlook PST Repair simply goes to work quickly and effectively.
• Multiple support packages: Stellar Phoenix Outlook Repair comes with three different pricing plans. One is designed for people who only need to install the program on a single computer. Another is designed for businesses or households that want to install the program on multiple PCs.And with the third option, the technician package, users can install Stellar Phoenix Outlook PST Repair on an unlimited number of computers. One of the biggest advantages of these packages is that you can spread out the cost of the program among multiple users. If several different people at your workplace are having PST error problems, for example, then you can buy a multiple-license package and share the cost.
• Data recovery: Along with fixing corrupt PST files and removing the size limits from the PST file, Stellar Phoenix Outlook PST Repair can actually recover any Outlook data on your computer. This is useful if you uninstalled Outlook a few months ago but still need to recover that data. In fact, Stellar Phoenix can recover Outlook data even if Outlook is not currently installed on your computer. In that sense, Stellar Phoenix Repair is more than just an Outlook repair program; it’s also a full-service data recovery solution.

Stellar Phoenix PST Repair is superior to ScanPST.exe in every way. But Stellar Phoenix’s most important advantage is that it actually works. If you’re ready to quickly fix your Outlook PST errors, then Stellar Phoenix Outlook PST Repair can help. Download it here today to experience the magic of PST repair for yourself.

Windows photo viewer was a popular photo viewing application integrated into Windows 7, 8, and 8.1 but in Windows 10 it has been replaced with photos, Microsoft's new application aimed at photo viewing on your desktop. Now if any one of you wonders why should be bringing the old application back to Windows 10 since we have an alternative one, the answer would be resources and speed. The old photo viewer application is lightweight, fast, and reliable, opening the same photo in both photo viewer and in new photos shows us that Microsofts new viewer application takes even three times more RAM, and it's visibly slower in loading times for pictures. Since I am a person who prefers speed and functionality over fancy looks I would be very glad to have the option to bring back a photo viewer. If you have by any chance Windows 10 as an upgrade, bringing back photo viewer is easy as 1,2,3. you just need to open settings and go to default apps, under photo viewer you should see your current default viewing application, probably photos, click on it to see options and choose photo viewer and exit the Settings menu, and you're done. Sadly if Windows 10 has been installed clean on the system and not as upgrade things are a little bit more complicated but do not worry, stay with us, keep reading and you will get there.

Activating photo viewer

How technically photo viewer is still in the system but not used we will have to make it available again and this we will do by adding some lines in the Windows registry, that being said, open a notepad and paste the following code as it is in it.

---

Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\jpegfile\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\pngfile\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\open] "MuiVerb"="@photoviewer.dll,-3043" [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Bitmap] "ImageOptionFlags"=dword:00000001 "FriendlyTypeName"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\ 00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,\ 77,00,73,00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,\ 00,65,00,72,00,5c,00,50,00,68,00,6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,\ 65,00,72,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,35,00,36,00,00,\ 00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Bitmap\DefaultIcon] @="%SystemRoot%\\System32\\imageres.dll,-70" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Bitmap\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Bitmap\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\print] "NeverDefault"="" [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\print\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\Applications\photoviewer.dll\shell\print\DropTarget] "Clsid"="{60fd46de-f830-4894-a628-6fa81bc0190d}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.JFIF] "EditFlags"=dword:00010000 "ImageOptionFlags"=dword:00000001 "FriendlyTypeName"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\ 00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,\ 77,00,73,00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,\ 00,65,00,72,00,5c,00,50,00,68,00,6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,\ 65,00,72,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,35,00,35,00,00,\ 00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.JFIF\DefaultIcon] @="%SystemRoot%\\System32\\imageres.dll,-72" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.JFIF\shell\open] "MuiVerb"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,\ 69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,\ 00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,\ 72,00,5c,00,70,00,68,00,6f,00,74,00,6f,00,76,00,69,00,65,00,77,00,65,00,72,\ 00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,34,00,33,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.JFIF\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.JFIF\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Jpeg] "EditFlags"=dword:00010000 "ImageOptionFlags"=dword:00000001 "FriendlyTypeName"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\ 00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,\ 77,00,73,00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,\ 00,65,00,72,00,5c,00,50,00,68,00,6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,\ 65,00,72,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,35,00,35,00,00,\ 00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Jpeg\DefaultIcon] @="%SystemRoot%\\System32\\imageres.dll,-72" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Jpeg\shell\open] "MuiVerb"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,\ 69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,\ 00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,\ 72,00,5c,00,70,00,68,00,6f,00,74,00,6f,00,76,00,69,00,65,00,77,00,65,00,72,\ 00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,34,00,33,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Jpeg\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Jpeg\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Gif] "ImageOptionFlags"=dword:00000001 "FriendlyTypeName"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\ 00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,\ 77,00,73,00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,\ 00,65,00,72,00,5c,00,50,00,68,00,6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,\ 65,00,72,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,35,00,37,00,00,\ 00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Gif\DefaultIcon] @="%SystemRoot%\\System32\\imageres.dll,-83" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Gif\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Gif\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Png] "ImageOptionFlags"=dword:00000001 "FriendlyTypeName"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,\ 00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,\ 77,00,73,00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,\ 00,65,00,72,00,5c,00,50,00,68,00,6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,\ 65,00,72,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,35,00,37,00,00,\ 00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Png\DefaultIcon] @="%SystemRoot%\\System32\\imageres.dll,-71" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Png\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Png\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Wdp] "EditFlags"=dword:00010000 "ImageOptionFlags"=dword:00000001 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Wdp\DefaultIcon] @="%SystemRoot%\\System32\\wmphoto.dll,-400" [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Wdp\shell\open] "MuiVerb"=hex(2):40,00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,\ 69,00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,\ 00,20,00,50,00,68,00,6f,00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,\ 72,00,5c,00,70,00,68,00,6f,00,74,00,6f,00,76,00,69,00,65,00,77,00,65,00,72,\ 00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,30,00,34,00,33,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Wdp\shell\open\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\PhotoViewer.FileAssoc.Wdp\shell\open\DropTarget] "Clsid"="{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}" [HKEY_CLASSES_ROOT\SystemFileAssociations\image\shell\Image Preview\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,75,00,\ 6e,00,64,00,6c,00,6c,00,33,00,32,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,\ 00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,\ 25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,50,00,68,00,6f,\ 00,74,00,6f,00,20,00,56,00,69,00,65,00,77,00,65,00,72,00,5c,00,50,00,68,00,\ 6f,00,74,00,6f,00,56,00,69,00,65,00,77,00,65,00,72,00,2e,00,64,00,6c,00,6c,\ 00,22,00,2c,00,20,00,49,00,6d,00,61,00,67,00,65,00,56,00,69,00,65,00,77,00,\ 5f,00,46,00,75,00,6c,00,6c,00,73,00,63,00,72,00,65,00,65,00,6e,00,20,00,25,\ 00,31,00,00,00 [HKEY_CLASSES_ROOT\SystemFileAssociations\image\shell\Image Preview\DropTarget] "{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}"="" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Photo Viewer\Capabilities] "ApplicationDescription"="@%ProgramFiles%\\Windows Photo Viewer\\photoviewer.dll,-3069" "ApplicationName"="@%ProgramFiles%\\Windows Photo Viewer\\photoviewer.dll,-3009" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Photo Viewer\Capabilities\FileAssociations] ".cr2"="PhotoViewer.FileAssoc.Tiff" ".jpg"="PhotoViewer.FileAssoc.Jpeg" ".wdp"="PhotoViewer.FileAssoc.Wdp" ".jfif"="PhotoViewer.FileAssoc.JFIF" ".dib"="PhotoViewer.FileAssoc.Bitmap" ".png"="PhotoViewer.FileAssoc.Png" ".jxr"="PhotoViewer.FileAssoc.Wdp" ".bmp"="PhotoViewer.FileAssoc.Bitmap" ".jpe"="PhotoViewer.FileAssoc.Jpeg" ".jpeg"="PhotoViewer.FileAssoc.Jpeg" ".gif"="PhotoViewer.FileAssoc.Gif" ".tif"="PhotoViewer.FileAssoc.Tiff" ".tiff"="PhotoViewer.FileAssoc.Tiff"

---

Yup, that is a lot of keys and settings but you are almost done. Once you have pasted text into your new notepad document save it but as .REG, you can name it however you want but it has to be .REG extension. Once the file is saved double click on it to merge it into the Windows registry. You might need to turn off UAC for this operation (check our tutorial on this topic) and accept warning messages but once it is done you should now have an old photo viewer as a choice for your default viewing application. All you have to do now is to go to settings and go to default apps, under photo viewer you should see your current default viewing application, probably photos, click on it to see options and choose photo viewer and exit the Settings menu, and you're done.

When Microsoft held Windows 11 presentation it took special time to present the upcoming new Windows 11 store as kind of a big deal. It was openly stated that with new Windows we will get a new store with a different attitude and new look.

New Microsoft store

Microsoft has stated that both customer and developer feedback over time has contributed to their redesign and rethinking of the store itself. They want to be sure that policies for developers are more straightforward and clear so more developers will decide to bring their product to Windows. As for customers, they want more safety and more security so they feel protected when making a purchase. The new store will come in Windows 11 but also in Windows 10 as well via update.

Stories and collections

Introducing the new store will be curated stories. Microsoft believes that stores should be focused on user experience so stories from customers themselves will play a big role here. They are rich editorial content to keep you informed about the best apps and inspire you to achieve more with your device. This approach to information is aimed at bringing unknown applications to users via presenting them in a professional manner. Android apps in the store As stated in Windows 11 unveiling and presentation, Android apps will work inside Windows 11. Microsoft has teamed up with Amazon to bring you Android apps directly inside Windows via the new Microsoft store.

Pop up store from within a browser

When you are surfing on a certain webpage and want to save and install the application from there, a new pop-up store window will show allowing you to install the app directly. Microsoft has not said will this feature work outside their Edge browser so we will have to wait and see about that.

Support for multiple types of applications

Since now developers were tied to certain formats if they wanted to publish their application in any kind of environment. Microsoft wants to bridge this. Windows developers can publish any kind of app, regardless of app framework and packaging technology – such as Win32, .NET, UWP, Xamarin, Electron, React Native, Java, and even Progressive Web Apps. For Progressive Web Apps Microsoft has made open-source tool PWABuilder 3.

Flexibility and choice of commerce platform

Starting July 28, app developers will also have an option to bring their own or a third-party commerce platform in their apps, and if they do so they don’t need to pay Microsoft any fee. They can keep 100% of their revenue.

Both the DISKPART utility and the Disk Management are useful tools in Windows 10 that manage the disk space allocation, and so on. But these tools are not without errors as you could also encounter some when you run them. Recently, some users reported getting an error that says, “The selected disk is not a fixed MBR disk when trying to use the DISKPART utility”. Here’s the exact message of the error:

“The selected disk is not a fixed MBR disk. The ACTIVE command can only be used on fixed MBR disks.”

This kind of error only occurs when you try to activate a disk partition on a UEFI system partition. However, the command works only if your computer is based on BIOS/MBR. The UEFI method has no concept of the active partition and since you have a UEFI system, the disk type is GPT instead of MBR. To simply put it, your BIOS needs the MBR disk type while the UEFI needs the GPT disk type. To fix the “The selected disk is not a fixed MBR disk when trying to use the DISKPART utility” error, there are various potential fixes you can try. You might have to disable Secure Boot, convert the disk to MBR or fix the Boot Manager. For more instructions, follow the options provided below.

Option 1 – Disable the Secure Boot in the BIOS

Disabling the Secure Boot in the BIOS settings is definitely recommended to resolve the issue. 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 – Try converting the disk to MBR

You can try to change the File System of the drive from GPT to MBR but before you do so, make sure that you create a backup copy of your data to an external drive. Once you have that covered, follow the steps below.

• Create a bootable Windows 10 media and boot your computer from it.
• Next, click on the “Repair your computer” option on the first Windows 10 installation setup window.
• Afterward, select the operating system partition from the given options and click on Next.
• Now select Command Prompt within the System Recovery options box and execute this command to initiate the Diskpart utility: diskpart
• Then type either one of these commands to view the list of all the Disk connects or the partitions on those disks formed: list disk or list volume
• After that, execute another one of these commands depending on the command you previously entered to select the disk or partition you want to select: select disk # or select volume #
• Now execute this command to clean your drive: clean
• Finally, execute this last command to convert the selected disk or partition as MBR: Convert MBR
• Restart your computer and check if the error is fixed.

Option 3 – Try to fix the Boot Manager

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