Hello,

Sign up to join our community!

Welcome Back,

Please sign in to your account!

Forgot Password,

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

You must login to ask a question.

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

  1. This answer was edited.

    Windows' built-in Previous Versions feature is limited to full-drive protection because it relies on Volume Shadow Copies, a technology designed for low resource usage while backing up the entire drive, including locked, in-use, and protected files. If you need to protect only a specific folder, you'll need to explore other methods. Here are two suggestions: > Move the folder to a secondary hard drive and enable recovery functions on that drive. > Use a different backup tool that allows for single-folder protection.

    Windows’ built-in Previous Versions feature is limited to full-drive protection because it relies on Volume Shadow Copies, a technology designed for low resource usage while backing up the entire drive, including locked, in-use, and protected files.

    If you need to protect only a specific folder, you’ll need to explore other methods. Here are two suggestions:

    > Move the folder to a secondary hard drive and enable recovery functions on that drive.
    > Use a different backup tool that allows for single-folder protection.

    See less
  2. "Using 'Page Info > Media' works for me, but I recommend trying 'Developer Tools > Network': press F12 to open DevTools, go to the 'Network' tab, filter by 'Images', and refresh the page with F5. This method displays both the 'Transferred' size (including HTTP headers and compression) and the actual 'Size' of the file."

    “Using ‘Page Info > Media’ works for me, but I recommend trying ‘Developer Tools > Network’: press F12 to open DevTools, go to the ‘Network’ tab, filter by ‘Images’, and refresh the page with F5.

    This method displays both the ‘Transferred’ size (including HTTP headers and compression) and the actual ‘Size’ of the file.”

    See less
  3. The "Windows Update cannot currently check for updates" error can occur due to a variety of reasons, such as corrupted system files, a misconfigured Windows Update service, or network issues. To resolve this error, you can try running the Windows Update Troubleshooter, resetting the Windows Update components, or checking your internet connection and firewall settings to ensure they are not blocking Windows Update.

    The “Windows Update cannot currently check for updates” error can occur due to a variety of reasons, such as corrupted system files, a misconfigured Windows Update service, or network issues.

    To resolve this error, you can try running the Windows Update Troubleshooter, resetting the Windows Update components, or checking your internet connection and firewall settings to ensure they are not blocking Windows Update.

    See less
  4. No, it doesn't make a difference. If you're using Cmd.exe, most of your commands are external, meaning they start an .exe as a separate process. This means their memory allocation only exists while the .exe is running. Once the process finishes, all of its resources (allocated memory, open files, etc.) are automatically cleaned up by the OS, not by Cmd.exe. In other words, resource cleanup is handled by your OS process management, not by the command shell, and the way you structure the command line doesn't affect it. This concern would be more relevant for commands that are internal to the shell. Cmd.exe has very few internal commands, whereas PowerShell allows for building large data structures within the shell's process. In theory, if you have PowerShell functions or cmdlets that handle large amounts of data, their objects might persist after the function returns. However, the CLR runtime will eventually perform garbage collection before it becomes a significant issue.

    No, it doesn’t make a difference.

    If you’re using Cmd.exe, most of your commands are external, meaning they start an .exe as a separate process. This means their memory allocation only exists while the .exe is running.

    Once the process finishes, all of its resources (allocated memory, open files, etc.) are automatically cleaned up by the OS, not by Cmd.exe.

    In other words, resource cleanup is handled by your OS process management, not by the command shell, and the way you structure the command line doesn’t affect it.

    This concern would be more relevant for commands that are internal to the shell. Cmd.exe has very few internal commands, whereas PowerShell allows for building large data structures within the shell’s process.

    In theory, if you have PowerShell functions or cmdlets that handle large amounts of data, their objects might persist after the function returns. However, the CLR runtime will eventually perform garbage collection before it becomes a significant issue.

    See less
  5. This answer was edited.

    Open the Camera desktop app, it will indicate that the Media Feature Pack is missing or available. Suggested path (Settings > Apps > Optional features) is mostly incorrect. Instead used the search bar in Settings to find Optional features. After installing the Media Feature Pack from there and restarting computer, the camera should work fine.

    Open the Camera desktop app, it will indicate that the Media Feature Pack is missing or available. Suggested path (Settings > Apps > Optional features) is mostly incorrect.

    Instead used the search bar in Settings to find Optional features. After installing the Media Feature Pack from there and restarting computer, the camera should work fine.

    See less