The Windows 10 system allows users to change the default location of the User folders to another drive. This is probably to make sure that the files stay safe in case the system suddenly crashes. However, in some cases, while changing the path to another drive, for instance, the D drive or any folder, the Windows system recognized it as a hard drive as well so even though the files will be saved on that folder, it will appear as a hard drive in the Windows Explorer or look merged with another folder. It could also be that you had dragged and dropped a user folder to another user folder by accident. So if you’re wondering how you can unmerge the User folders, read on as this post will guide you on how exactly you can do that.
Take note that even if you try to use the File History to restore the User folders, it still won’t work and you won’t be able to move them back to their previous locations nor restore the folders back to their previous versions and it would only state that they are not available. In the instructions given below, we are using the Downloads folder as an example.
ComputerHKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorerUser Shell Folders
%USERPROFILE%Downloads
Note: Look close enough and you’ll see that the multi-string values belong to each one of the folders. From there, you have a Desktop, Favorites, Skydrive, Music, Pictures, and many more.
Music – {1CF1260C-4DD0-4ebb-811F-33C572699FDE}
Pictures – {3ADD1653-EB32-4cb0-BBD7-DFA0ABB5ACCA}
Videos – {A0953C92-50DC-43bf-BE83-3742FED03C9C}
Documents – {A8CDFF1C-4878-43be-B5FD-F8091C1C60D0}
Desktop – {B4BFCC3A-DB2C-424C-B029-7FE99A87C641}
Some users wanting to upgrade to Windows 10 from Windows 7 or Windows 8.1 experienced errors with installation. One of these errors is CPU Not Compatible. When you click and run the “Get Windows 10” from your system tray bar, you’ll receive the “CPU is not compatible with Windows 10” error. When this happens, it might be good to check if there’s a bug or if your NX feature (a requirement for the Windows 10 installation) is enabled.
The “CPU is not compatible with Windows 10” error normally occurs when:
To successfully upgrade to Windows 10, your CPU must support Physical Address Extension (PAE), SSE2, and NX features. If any of these features are not activated on your system, it’ll cause the CPU not compatible error. However, some users still reported experiencing this error even though their CPU has these features activated. Normally, this is due to the bug that Windows acknowledged.
If any of these two scenarios apply to your computer, the following methods will help you fix the problem:
The bug applies to some Windows 7 and Windows 8.1 systems. The bug occurs when the “Get Windows 10” app fails to recognize CPUs as being compatible. This produces a false negative result with a message, “Here’s why Windows 10 cannot be installed on this PC: The CPU isn’t supported”. To fix this bug, Microsoft released an update.
Unfortunately, the patch update (KB2976978 for Windows 8/8.1 and KB2952664 for Windows 7 SP1) to fix the bug may not be automatically downloaded to your computer. If this is the case, you need to verify first if the patch was installed correctly. To do this, follow the steps below:
A major requirement for Windows 10 upgrade is for the CPU to have Physical Address Extension (PAE), SSE2, and NX features enabled on your system. If you receive the CPU not compatible error, one possible cause is that any of the mentioned features are not available OR not enabled on your system. Here’s how you can fix this:
If changing the settings in your BIOS doesn’t do the trick, your final option is to force enable the NX bit in your Windows system. However, this is only applicable IF and ONLY IF your CPU does support it. To force enable NX bit, do the following:
ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionAuthenticationLogonUITestHooksStep 4: From there, look for a DWORD named “ConsoleMode”. If you don’t see this DWORD, you can just create a new DWORD and name it as “ConsoleMode” and make sure that its base is set to Hexadecimal. Step 5: After that, double click on ConsoleMode and change its value to “0” to disable it and “1” to enable it. Step 6: Now restart your computer to apply the changes made. Like pointed out, you can only use your keyboard when you’re in the Console Mode login window or screen. You can just use the ESC button to go back to the menu while you can utilize the arrow keys so you can go through the options that are mostly vertically arranged and the Enter key to select an option. In the Console Mode, sign-in using the Passwords and PINs worked efficiently.
“Updates failed There were problems installing some updates, but we’ll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: 2018-07 Cumulative Update for Windows 10 Version 1803 for x64-based Systems (KB4345421) – Error 0xca00a000”This kind of Windows Update error pops up when Windows has missed installing one of the cumulative updates needed or when there is some problem with the driver that won’t let the installation of the updates push through. There are also instances when the system files are modified with incorrect permission that may result in the Windows update error 0xca00a000. Thus, you need to fix the trusted installer permission as well as resolve the issue with the driver. To do these things, you need to follow the options laid out below.
SC config trustedinstaller start=auto
net stop wuauserv net stop bits
net start wuauserv net start bitsSince the folder has already been flushed, it will be populated afresh the instant your restart your computer and open Windows Update.
KMODE_EXCEPTION_NOT_HANDLED – win32kbase.sys
PAGE_FAULT_IN_NONPAGED_AREA – win32kbase.sysThe win32kbase.sys file is a Windows operating system Base Win32 Kernel Driver file located in the System32 folder so if it ends up getting corrupted or if it went missing, your computer will throw up Blue Screen error. To fix BSOD errors that have something to do with the win32kbase.sys file, here are some possible fixes that could help. Worry not for these possible fixes are not complicated.
chkdsk /f C: