Fix Failed to transfer logged messages ...

In today's IT world, if you want a computer for typical day-to-day actions and gaming, there are 3 primary ways you can go. An Apple computer with its proprietary hardware and operating system or a typical machine with Windows or Linux operating system.

Each system has both advantages and disadvantages and picking the right one might be difficult for some users. From hardware differences to specific software and operating system, each system is aimed at a different type of work, and in this article, we will explore each one and help you in choosing the right one for you.

Apple ecosystem

Apple has managed to create a unique ecosystem of its own devices, from its iMac desktop computers to more professional MAC studio and power MAC and all the way to tablet iPad and iPhone are powered by Apple's own operating system that connects all of these devices into one large system. So if you really need one singular ecosystem this is a huge advantage.

The ecosystem on the side, MAC computer systems are great, some would argue best for coding, design, video work, and sound editing. MAC M2 chip is optimized for all of these tasks and a specially tailored operating system is just the icing on the cake. Specific Apple-made software like a logic pro or final cut also helps a lot to position MAC systems on top of the line.

Reading all of this you might think hey this is the computer for me, it does everything! Sadly the truth is not like that. The first thing that is difficult on MAC systems and a maybe big reason that it is not so adopted outside professional working environment is lack of games. If you are a gamer or plan on using MAC for gaming, well I have some bad news. The second big turn-off is that MAC systems tend to be more expensive than PC systems, yes components are of higher quality but rest assured that you will pay for also for branding.

Get MAC as your workstation for serious work and for good tech support, if you need a plain home computer keep reading.

Windows PC machine

There is no better feeling than assembling your own computer, tweaking hardware to make a monster and despite haters hating, Windows is the best all-around operating system on the market. It is supporting the largest variety of hardware and the largest variety of software.

The best platform for serious gaming and streaming Windows machine has cemented itself as a multimedia powerhouse. But, this kind of computer is not alien to being also a professional machine, you can practically do everything that you can do on Apple or Linux machine inside Windows, yes some things might require extra steps or will be slightly slower but in the end, being able to do anything is the greatest strength of Windows machine.

Of course, every system has its flaws and Windows is not immune to that. One of the biggest is being the operating system for every hardware ever made and every software as well while keeping legacy support for old software and hardware, basically, its biggest strength is in the same time its biggest weakness leading to sometimes stability issues. Also being able to place any kind of hardware can also lead to the same stability issues. Executing something a little slower than other systems and having some extra steps can also be looked upon as weaknesses.

Linux system

First and perhaps for some people, the biggest advantage of the Linux operating system is its price, it is completely free! Other advantages include the great server and networking included in the OS itself, the large amount of customization, and unmatched stability. The ability to write scripts inside the OS terminal is also a great thing and coding is much more streamlined and friendlier than on other machines.

The power of Linux is the ability to change anything, even on the system layer, no other operating system will let you change the basic functionality of the OS itself while Linux will let you do this. It is also the only operating system you can fully use by booting it up from a USB stick and having the same experience as it was installed on a local hard drive. Among other OS mentioned earlier, Linux is by far the lightest one, taking the smallest amount of memory among the three.

The bad side of the Linux machine is the steep learning curve, among the three mentioned operating systems rest assured Linux is the most difficult to learn and be comfortable in it. The operating system will require you to know the hardware and how computers work in order to fully use its potential. Other things that place it behind are not so wide hardware support compared to Windows and the somewhat confusing distro model.

Linux versions come in form of different distro packages and first-time users will face many of them being left in awe of which one to choose. Also installing drivers and software via a package system can also be a tedious task as well, often being that some version of the driver will not work on the newer version of the Linux distro.

Get a Linux machine if you are well versed in computer technology, if you want great customization of the OS itself or if you do not want to spend money on OS and software since almost entire Linux software is open source.

You might be trying to play music files using the Windows Media Player, but were unable to do so since you encountered an error saying, “Windows Media Player Error – Server Execution Failed” error. If you encountered this error, worry not for this post will guide you on how to fix it using some potential fixes. In the error message, the “Server execution failed” indicates that the “wmplayer.exe” is still running or shutting down at that point and it is possible that it is stuck which is not able to close properly. To fix this error, there are several potential fixes you can try. The first one is to run the Video Playback troubleshooter. While you could also try to disable the WMP Network Sharing Service or register both the jscript.dll and vbscript.dll files. For more information, refer to the options provided below.

Option 1 – Try to run the Video Playback troubleshooter

The first thing you can do to fix the problem, you can try to run the Video Playback troubleshooter instead. To run it, simply go to Settings > Update & security > Troubleshoot. From there, scroll down until you see the Video Playback option and then click on the “Run the troubleshooter” button to get started. This troubleshooter will detect and automatically fix any problems related to video playback so it should help fix the error.

Option 2 – Try to disable the WMP Network Sharing Service

If the Video Playback troubleshooter didn’t work in fixing the problem, the next thing you need to do is disable the Windows Media Player Network Sharing Service. The WMP Network Sharing Service is used to share the libraries of the Windows Media Player to other users on the network as well as media devices using the Universal Plug and Play. And since you are not using any network here, then you can disable this service to fix the problem. How? Refer to the given steps below.

• Tap the Win + R keys to open the Run dialog box and type “services.msc” in the field and tap Enter to open the Services Manager.
• Next, look for the Windows Media Player Network Sharing Service from the list of Services and right-click on it.
• After that, click on the Stop option and see if it fixes the Windows Media Player error.

Option 3 – Try to register the jscript.dll and vbscript.dll files

• Tap the Win + X keys and from the menu select the Windows PowerShell (Admin) option to open an elevated Command Prompt.
• Next, type this command to register the jscript.dll file and click on the confirmation box: regsvr32 jscript.dll
• After that, execute the regsvr32 vbscript.dll command to register the vbscript.dll file.
• Once you’re done, these DLL files will be re-registered and should fix the Windows Media Player error.

Error 0x8004210A - What is it?

0x8004210A is a typical POP3 email error message. This error may sometimes occur when you try to check your Post Office Protocol 3 (POP3) email account. 0x8004210A error code hampers your ability to both send and receive e-mails on your Outlook account. Error 0x8004210A is displayed in any one of the following formats on your PC:

The operation timed out waiting for a response from the receiving (POP) server 0x8004210a Task 'SMTP server name - Sending and Receiving reported error' (0x8004210A): 'The operation timed out waiting for a response from the receiving (POP) server. If you continue to receive this message, contact your server administrator or Internet service provider (ISP).'

Error Causes

Error 0x8004210A occurs due to several reasons. However, some of the most common reasons include:

• Wrong port number for the POP incoming server
• Your connection to the mail server is too slow
• Incoming and outgoing emails are being scanned and stopped by an antivirus installed on your system
• The Outlook send and receive job is being blocked by Firewall
• You are sending and receiving large series of emails or large email attachments
• Registry issues

No matter what the cause of this error is, to resume email communication via Outlook and to ensure your work productivity is not affected, it is recommended that you resolve this 0x8004210A error code on your PC immediately.

Further Information and Manual Repair

To fix error 0x8004210A, here are some of the most efficient and easy manual methods that you can try:

Method 1

If the cause of the error is related to the internet connection then here’s what you need to do. Try freeing up your internet connection by closing any other online activities in progress or downloads being carried on your system.

Method 2

Try to increase your server time-out periods. To do this, go to the Outlook File menu and choose account settings. Now double click on your email account and more settings. Now click advanced and increase your server timeout period to resolve.

Method 3

If you are trying to send or receive large and heavy emails on your Outlook account, the error 0x8004210A may pop up. This happens because when transferring heavy files the email account automatically locks until the task is complete, however, if it takes more time the next Send and Receive job starts while the first one is still not complete. In such an event, the email server then times out and shows you the error. Therefore to resolve, you will have to show patience. Simply wait for the large email to be sent or received before you start sending another email.

Method 4

If the antivirus installed on your system is the reason for the error pop up, then disable it for a while until the operation is complete. Then enable it once the task is performed successfully.

Method 5

Similarly, if the Firewall installed on your system is preventing Outlook from reaching your mail server, then simply disable the Firewall to resolve.

If you got an error message saying, “Windows Update failed to install error 0x80240034” when trying to update your Windows 10 then it’s probably due to some update services that are failing at some point. In addition, you might also see Error constant WU_E_DOWNLOAD_FAILED with the description that “Update has failed to download”. The Windows Update failed to install error 0x80240034 might be caused by some connection problem or there might be a duplicate update or that installation is not allowed and so on. And so to fix the problem, we’ve prepared some options that could help. Make sure to follow them accordingly but before you proceed, you need to verify if you have a stable internet connection.

Option 1 – Restart your computer and try installing the Updates again

Restarting your computer can also help in fixing the Windows Update failed to install error 0x80240034. There are cases where the issue resolves on its own as it could just be some simple network or PC error.

Option 2 – Try to disable your antivirus program

The Windows Update failed to install error 0x80240034 might be caused by the antivirus program installed in your computer which is why disabling the antivirus program or any security software installed in your computer is always a good idea you can try when the Windows Update process does not go smoothly. So before you try updating your computer again, make sure to disable the antivirus or security program and once the Windows Update is done, don’t forget to enable the antivirus program back again.

Option 3 – Clean up temporary and junk files

• Open Setting > System > Storage from the WinX Menu.
• From there, you will see a list of all the local and connected storage devices along with the details on the free space.
• Now make sure that the Storage Sense feature is turned On then go find a link that says “Free Up Space” and click it to open.
• After that, a screen which is the built-in program in Windows 10 will appear and will scan your computer for the following junk files so you can free up disk space:
• Windows Upgrade Log Files
• The system created Windows Error Reporting Files
• Thumbnails
• Temporary Internet Files
• Previous Windows Installation Files
• Delivery Optimisation Files
• DirectX Shader Cache

Note: Once you’re done freeing up space on your drive, try to run the setup file again.

Option 4 – Run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter is one of the things you can first check out as it is known to automatically resolve any Windows Update errors like error 0x80240034. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 5 – Delete Files from Software Distribution Folder & Catroot2 folders

The downloaded Windows Updates are placed in a folder called “SoftwareDistribution”. The files downloaded in this folder are automatically deleted once the installation is completed. However, if the files are not clean up or if the installation is still pending, you can delete all the files in this folder after you pause the Windows Update service. For complete instructions, refer to the steps below.

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net start cryptSvc net start bits net start msiserver

• After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
• Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.

After resetting the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:

• Type each one of the following commands.

net start wuauserv net start cryptSvc net start bits net start msiserver

• After that, exit Command Prompt and restart your computer, and then try to run Windows Update once more.

Option 6 – Run the DISM tool

If the first five options didn’t work, then running the Deployment Imaging and Servicing Management tool might help as it can repair the Windows System Image as well as the Windows Component Store in Windows 10.

• After you access the Advanced Startup options, select Command Prompt by using the arrow keys on your keyboard.
• Next, type in this command: DISM /Online /Cleanup-Image /RestoreHealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 7 – Run System File Checker

Running the SFC scan or System File Checker might also help in fixing error 0x80240034.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow and hit Enter.
• Restart your PC.

Option 8 – Try to use the Media Creation tool

The Media Creation tool in Windows allows you to use the ISO installation file to make a bootable device that you can use to install Windows on your PC. Note that this is kind of different from the usual installation process as it could erase your computer’s current settings and data on the primary drive. Thus, before you proceed, you need to backup all your data into some removable drive and then use the Media Creation Tool to make a bootable drive.

• After making the bootable drive, you need to plug it into your computer and then reboot.
• Next, tap the F10 or Esc key to open the boot options.
• Now set the boot priority of the removable drive the highest. Once the setup comes forth, follow the next onscreen instructions and install Windows without any problems.

There are times when the Windows Search doesn’t work and you wouldn’t have a clue as to why it happened since it does not give any error codes. In such cases, you have to check the error logs in the Event Viewer to find out more about the problem. From there, look for an error with the Event ID 3104 in the Windows error logs and if you see an error message that says, “Enumerating user sessions to generate filter pools failed”, read on as this post will guide you in fixing the problem. Apart from the error message, you might also see more information in the details section of the log that says, “(HRESULT: 0x80040210) (0x80040210)”. This kind of error is most likely caused by something that prohibits the search function from initializing. A lot of users assumed that it could be due to Cortana but it’s actually not. While some users also reported that they encounter the issue after they restarted their computers. This error was also reported with the same event ID 3104 on the Windows Server. According to security researchers, this error could be caused by problems in the Registry entry of Windows search. It could also be due to an issue with the SYSTEM account where it hasn’t been added to the DCOM Security. It is also possible that the Windows Search function has not been initialized. To fix this error, you can try to rebuild the Search Index manually or run the Search and Indexing troubleshooter. You can also check the startup type of the Windows Search service or try some registry tweak.

Option 1 – Try to rebuild the Search Index manually

The first thing you can do to fix the problem is to manually rebuild the Search Index. You can do that by going to Control Panel > Indexing Options and from there, click on Advanced. After that, go to the Index Settings tab and then click on Rebuild > OK. Once you’re done, check if it fixed the problem.

Option 2 – Try running the Search and Indexing troubleshooter

You could also run the Search and Indexing troubleshooter in Windows 10 as it checks whether the settings are in place and automatically corrects any issues with the Windows 10 search function. To run this troubleshooter, just click on the Start button and select Settings > Updates and Security > Troubleshoot. From there, select the Search and Indexing Troubleshooter. Once the troubleshooter is done, restart your computer and see if it fixed the error.

Option 3 – Try checking the startup type of the Windows Search Service

In this option, you have to check the startup type of the Windows Search service since the service won’t start. To do so, refer to these steps:

• Tap the Win + R keys to open the Run utility and type “services.msc” in the field and then tap Enter to open the Services Manager.
• Next, from the list of services, look for the Windows Search Service or WSearch. Once you find it, right-click on it and select Properties.
• After that, change the Startup type to Automatic and click on the Start button if the service is in the Stop state.
• Now click on the Apply and OK buttons to save the changes made and then restart your computer.

Option 4 – Try changing the Registry entry for Windows Search

Before you apply some registry tweak, you need to create a System Restore point first. Once you have that covered, follow these steps:

• Tap the Win + R keys to open the Run utility and type “Regedit” in the field and tap Enter to open the Registry Editor.
• If a User Account Control prompt appears, just click Yes to proceed.
• After opening the Registry Editor, navigate to this registry path: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows Search
• From there, click on Windows Search and look for the key named “SetupCompletedSuccessfully” and change its value to “0”. Just right-click on it and select Modify.
• Then input “0” as its value data and click on OK to save the changes made.
• Exit the Registry Editor and restart your computer.
• Now check if the Enumerating user sessions to generate filter pools failed is fixed or not.

The Blue Screen of Death error or BSOD is definitely not an issue to face on your computer. Many users, if not all, have already experienced this headache at least once. One of these BSOD errors is the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY error. The bug check error code for this is 0x000000FC and is usually caused by outdated or faulty drivers. In some cases, it could also be caused by an error in the Random Access Memory or RAM. This kind of error in the RAM might be physical, based on drivers, or even some kind of unwanted malware. So basically there are lots of possibilities why this particular BSOD error pops up. If you are currently facing this BSOD error, read on and carefully follow the suggestions given below but before you do that, make sure to create a System Restore point just in case something goes wrong. This way, you can always undo those changes using the System Restore point. Once you have that covered, proceed to the options given below to fix the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY error.

Option 1 – Try updating Windows 10 with all the security patches and updates

You might be able to fix the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY error by simply updating your Windows 10 computer with all the security patches and updates. To do so, go to Settings then proceed to the Windows Update section > Update & Security > Windows Update, and then click on the Check for Updates option. After you do that, it will automatically find and install all the latest security patches and feature updates from Microsoft.

Option 2 – Try updating all your drivers

From time to time, drivers get corrupted or outdated so it’s no surprise that they conflict with the operating system and cause errors like the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY BSOD error. To fix the problem, you need to update all your drivers. Follow the steps below to update your drivers.

• Tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. If you see a red or yellow sign that shows up against the driver, right-click on the driver’s name and select “Update Driver Software” or “Uninstall”. And if you find any “Unknown device”, you need to update it as well.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• Restart your PC.

Note: You also have the option to go directly to the website of your graphics card manufacturer and check if there’s a new update – if there is, download it.

Option 3 – Try running a Memory Check using Windows Memory Diagnostic

As mentioned, this error might be caused by some issues in the memory. To resolve it, you need to run the Memory Check on your Windows 10 PC. Refer to these steps to do so.

• Tap the Win + R keys to open the Run dialog box.
• Then type “mdsched.exe” in the field and hit Enter to open the Windows Memory Diagnostic.
• After that, the Windows Memory Diagnostic will give out two options such as:

1. Restart now and check for problems (recommended)
2. Check for problems the next time I start my computer

• Select any of the given options. After that, your computer will restart and check for memory-based issues upon the restart. If there are any issues, it will automatically them.

Option 4 – Try using the System File Checker via Command Prompt

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 with good system files that might be causing the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY BSOD error. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

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.

There are a lot of home users that often get a computer that comes installed with the Windows 10 Home. And since Windows 10 Pro offers more features and utilities compared to Windows 10 Home, a lot of users also prefer to upgrade their Windows 10 Home computers to Windows 10 Pro. However, while doing so, a number of users reported that they encountered error 0xc03f6506 and they were not able to proceed with the upgrade. If you are one of these users, when you encounter error 0xc03f6506, you will see the following error message on your screen:

“The last product key you entered can’t be used on this copy of Windows (0xc03f6506).”

This particular error tends to occur when you go on to activate Windows 10 although it can also appear during the upgrade process. In such cases, you will see the following error message:

“Unable to upgrade your edition, We can’t upgrade your edition of Windows. Try upgrading your edition of Windows again. (0xc03f6506).”

To fix the Activation Error Code 0xc03f6506 in Windows 10, use the options provided below as references but before you proceed, make sure that you create a System Restore point first.

Option 1 – Try to use the Registry Editor

If you have already upgraded from Windows 10 Home to Windows 10 Pro and you’re having trouble with its Activation, then you might want to apply some registry tweaks to fix the problem. How? Refer to these steps:

• Tap the Win + R key combination to open the Run dialog box.
• Then type “Regedit” in the field and click OK or tap Enter to open the Registry Editor.
• Next, navigate to this registry key: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersion
• From there, look for a DWORD named “EditionID” and once you found it, double click on it and change its Value data to Windows 10 Professional.
• After that, look for another DWORD named “ProductName” and double click on it to change its Value data to Windows 10 Professional.
• Once you’re done, restart your computer to apply the changes made successfully.

Option 2 – Try to use Command Prompt

If the registry tweaks you applied didn’t fix the Activation error, then you can try using Command Prompt instead. Note that you can use this option in both scenarios pointed out above.

• First, you have to insert a bootable drive of the Windows10 installer.
• Next, tap the Win + X keys and select Command Prompt (Admin) from the menu.
• After opening Command Prompt as admin, navigate to the root location of the bootable drive inside the Command Prompt command line.
• Once you’re already there, type the following command and tap Enter:

setup.exe /auto upgrade /pkey <YOUR WINDOWS 10 PRO EDITION PRODUCT KEY>

After entering the command, check if it was able to fix the Windows Upgrade or Activation error 0xc03f6506. If not, refer to the next given option below.

Option 3 – Try to disable the Network Adapter

Just like the second option, you can also use this option for both the given scenarios above.

• Tap the Win + X keys and select Network Connections from the menu.
• This will open the settings for your network and on the left side panel, click on the “Change adapter settings” link. This will open Control Panel.
• From there, click on the network your computer is connected to, and then right-click on the Network Adapter that you are using and select Disable.
• After disabling the Network Adapter, try to switch to the edition of your copy of Windows 10 again and see if the problem is now fixed and don’t forget to double click on the disabled Network Adapter to get back on the Network.

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.

What is BitCoinMiner Malware?

BitCoinMiner is a Malware created with the intent to force computer systems to generate crypto-currency, namely Bitcoin. This is done without the consent and knowledge of a computer/system holder. This unwanted file bears no digital signature or publisher since the creators of such a heinous invention do not wish to be known. Technical details about BitCoinMiner Malware include:

Product Version: 1.0.0.0 Original File Name: crss.exe Entry Point:  0x000C5AAE

Assessment of BitCoinMiner Malware

After installation of the BitCoinMiner Malware, there were no visible signs of an infection or program files installed. However, based on research, BitcoinMiner Malware utilizes the CPU’s resources (est. to be about 50%). Computer users have reported that they recognized an unknown process utilizing the majority of their processing space. the bitcoin miner is used by the creators to penetrate a user’s system, in effect coercing each infected system to mine Bitcoins covertly. After years of mining, a user might discern that their computer is moving slouchy and may even encounter various forms of BSODs.   After Bitcoins have been mined in the infiltrated system, the cyber currency is then returned/ sent to the creator of the malware. This venture is a sly and deceptive way to earn Bitcoins since the currency is gaining much popularity.

Further Information on BitCoinMiner

BitCoinMiner works covertly. There are no obvious traces of this program running on a computer system. However, once a computer system is infiltrated, the computer user will realize that their CPU resources are strangely being used up, even while the computer idles. Another expression of BitCoinMiner is the addition of cookies of various sorts to a computer system. These include:

• Tracking cookies
• Advert (Adware) cookies
• Casale Media (Spyware) cookies
• Atwola (Spyware) cookies
• Adtech (Spyware) cookies

Once BitCoinMiner is present on a computer system, it can potentially slow it down and also create back doors as a means to install other unwanted and harmful programs. To completely remove BitCoinMiner Malware from your computer, click here to download and install Spyhunter.

Caching is used to enhance the performance of applications in Windows and other operating systems. It helps applications to load faster but there are times when the cache can get damaged or corrupted and as a result, you might encounter some issues. One of them is in the Firefox browser where the “Your Firefox profile cannot be loaded, It may be missing or inaccessible” error message may appear. You could also encounter this kind of error when Firefox is unable to access or find the profile folder. In case you don’t know what the profile folder is, it is where Firefox stores your user data and settings by default. Firefox pulls information from this folder each time you choose to open it. You can find this default Firefox profile folder under the %APPDATA%MozillaFirefoxProfiles folder. If you experience issues when trying to access the Profile Manager, you have the option to create a new default Firefox profile folder. This will fix the “Your Firefox profile cannot be loaded, It may be missing or inaccessible” error. How? Simply follow the given steps below. Step 1: Tap the Win key or click the Windows Start button to open the Start menu. Step 2: Next, type “%appdata%” in the field and hit Enter to open the hidden AppDataRoaming folder. Step 3: Now double click the Mozilla folder as well as the Firefox folder. Step 4: From there, look for the “profiles.ini” file and delete it. Make sure that you don’t delete the Profiles folder which should have the icon of a file folder. Note: Keep in mind that the .ini file extension is identified as the file that features a gear icon beside the “Configuration settings” or “Application settings”. Step 5: Once you open Firefox, a new profile will be created. On the other hand, if you know where your profile exists, you can try the following steps below to help Firefox locate it.

• First, you need to move the profile folder back to its original location.
• Next, restore the profile folder’s original name if you have modified it.
• Then create a new profile using the Profile Manager and give it an appropriate name.
• Now click on the Choose Folder button and select the profile folder you have moved or renamed before you exit the Create a new profile wizard.