Thank you for your support! ❤

@MikeFitzpatrick-vr4ic Thank you so much for your kind words! 😊 I’m really glad the Command Prompt method worked for you and that you could give your laptop a second life instead of turning it into e-waste. That’s exactly why we make these tutorials-to help people make the most of their devices. If you have any other questions or need help in the future, feel free to reach out! Please note that using Rufus for the upgrade does not require changing boot settings, and we perform the upgrade within the same Windows environment without restarting.

Hi @Brassmonger, Thank you for sharing your experience. I'm sorry to hear your PC went into an endless reboot after resetting the network settings. This is definitely not the usual behavior, and I’d like to help you troubleshoot this issue. Here are a few steps you can try to resolve the problem: 1. **Boot into Safe Mode via Windows Recovery Environment (WinRE):** How to Enter Windows Recovery Environment in Windows 10 kzbin.info/www/bejne/iKK4g6hoosiomtE If your PC is stuck in an endless reboot, forcefully shut it down by holding the **power button** until it turns off. Repeat this process 2-3 times. This will trigger Windows Recovery Environment (WinRE) on the next startup. Once in the recovery menu: - Select **Troubleshoot**. - Go to **Advanced options** > **Startup Settings**. - Click **Restart**. After the PC restarts, you’ll see a list of options. Press: - **4** or **F4** to boot into Safe Mode. - **5** or **F5** for Safe Mode with Networking. Once in Safe Mode, check if the reboot issue persists and proceed with the troubleshooting steps. 2. **Reset Network Settings in Windows 10 using CMD** Open the Start menu. Type cmd and run it as administrator. Decline restarting your machine until you have entered the final command. At the command prompt: a. Type "ipconfig /release" and press Enter. b. Type "ipconfig /flushdns" and press Enter. c. Type "ipconfig /renew" and press Enter. (This will stall for a moment.) d. Type "netsh int ip reset" and press Enter. (Don’t restart yet.) e. Type "netsh winsock reset" and press Enter. Close command prompt and restart the computer at the end of all the commands. All network settings or adapters will be reset. 3. **Check for Driver Issues:** - It’s possible that the network adapter driver is causing the issue. In Safe Mode: - Open **Device Manager** by pressing **Windows key + X** and selecting it from the menu. - Expand **Network adapters**, right-click your adapter, and choose **Uninstall device**. Restart your PC to allow Windows to reinstall the driver automatically. 4. **Repair Startup:** - If your PC still won’t boot properly, use the **Startup Repair** tool: - Boot from a Windows installation media (USB/DVD). - Select **Repair your computer**, then go to **Troubleshoot > Advanced Options > Startup Repair**. 5. **Undo Network Reset:** - If you’re able to boot into Safe Mode, you can try restoring your system to a previous state using **System Restore**: - Press **Windows key + R**, type `rstrui`, and press Enter. - Follow the instructions to restore your PC to a point before the network reset. 6. **Contact Support or Check Hardware:** - If none of these steps resolve the issue, it might be related to hardware or other software conflicts. Consider reaching out to your PC manufacturer or a professional technician for further assistance. Please let me know how these steps work for you, and if you have any other questions, I’m here to help!

Hello! As a workaround, you could try enabling the execution of scripts system-wide. Here’s how: 1. Open **PowerShell** as an administrator. 2. Run the following command: Set-ExecutionPolicy RemoteSigned -Scope LocalMachine 3. Confirm the change when prompted and test the shutdown sound again. We’ve tested this method exactly as shown in the video on Windows 11 version 24H2, and it worked perfectly. For further assurance, we tested it again to ensure it works correctly. If you’ve followed the steps exactly as demonstrated, it should work as well. If the issue persists, I suggest following the instructions at the end of the video to delete the service and files, then reapply the tutorial steps from the beginning. This can help if something went wrong during the initial setup. Let me know if you need further assistance! 😊

SSE4.2 stands for **Streaming SIMD Extensions version 4.2**, which is a CPU instruction set used by modern software and operating systems, including Windows 11, for improved performance and functionality. In the context of upgrading to Windows 11 24H2, a CPU that does not support SSE4.2 will not be compatible with this version. As mentioned in the video, the system may fail to boot if you try to install Windows 11 24H2 on a processor that lacks SSE4.2 support. If you're unsure whether your CPU supports it, you can check your processor's specifications on the manufacturer's website or by using tools like CPU-Z. Let me know if you need further assistance! 😊

@cnatt Thank you very much for your kind guidance.

You’re very welcome! 😊 I’m glad the guidance was helpful to you. If you have any other questions or need further assistance, feel free to ask anytime. Thanks for watching and supporting the channel! 🙏

@cnatt Thanks once again.

Hello! As a workaround, you could try enabling the execution of scripts system-wide. Here’s how: 1. Open **PowerShell** as an administrator. 2. Run the following command: Set-ExecutionPolicy RemoteSigned -Scope LocalMachine 3. Confirm the change when prompted and test the shutdown sound again. We’ve tested this method exactly as shown in the video on Windows 10 version 22H2, and it worked perfectly. For further assurance, we tested it again to ensure it works correctly. If you’ve followed the steps exactly as demonstrated, it should work as well. If the issue persists, I suggest following the instructions at the end of the video to delete the service and files, then reapply the tutorial steps from the beginning. This can help if something went wrong during the initial setup. Let me know if you need further assistance! 😊

Thank you for your comment! As a workaround, you could try enabling the execution of scripts system-wide. Here’s how: 1. Open PowerShell as an administrator. 2. Run the following command: Set-ExecutionPolicy RemoteSigned -Scope LocalMachine 3. Confirm the change when prompted, and then test the shutdown sound again. We’ve tested this method again on Windows 10 version 22H2, and if you follow the steps correctly, it should work just as described in the video. For added assurance, we tested it once more to ensure it functions properly. Also, it would be a good idea to disable Fast Startup in Windows 10, as it can sometimes interfere with certain settings. After disabling Fast Startup, perform a restart and check if the problem is resolved. You can follow this tutorial to disable Fast Startup: [How to Enable or Disable Fast Startup in Windows 10](kzbin.info/www/bejne/qnnXn4Kke9Staac) Let me know if you need further help!

Hi @bassquik0146, thank you for sharing your solution! 😊 You're absolutely right-using the command to modify the registry is a great way to make the "Hibernate After" option appear in the advanced settings. For others who might face the same issue, here’s the command again: ``` REG ADD HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\238C9FA8-0AAD-41ED-83F4-97BE242C8F20\9d7815a6-7ee4-497e-8888-515a05f02364 /v Attributes /t REG_DWORD /d 2 /f ``` Simply open Command Prompt as an administrator, paste the command, and press Enter. Once done, the "Hibernate After" option should appear in the Power Options menu. Thanks again for contributing to the discussion and helping others in the community. Let me know if you have any more tips to share! 😊

Hi @realspyrakos! It sounds like you might be encountering a permissions issue. This can happen if you're using a user account without administrative rights. Here’s how you can fix it: 1. **Switch to an Administrator Account:** - Check if your current account has admin privileges. - If not, log in with an administrator account or ask the admin of your device to grant you permissions. 2. **Run as Administrator:** - When disabling Windows Defender, make sure you run the settings or commands as an administrator. - Right-click on the Windows Security app or any commands you’re using and select **"Run as administrator."** 3. **Check Organizational Settings:** - If you're using a work or school device, IT administrators may have restricted access to certain features. You’ll need to contact your IT support team for assistance. Let me know if you need more help-I’m here to assist! 😊

Hi there! Thanks for your comment. Could you please clarify the issue you're facing? Are you referring to a specific step in the process, or is the toggle to disable Windows Defender not working? If Windows Defender re-enables itself automatically, that's expected behavior to ensure your system remains protected. Let me know the exact problem you're encountering, and I'll do my best to help! 😊

Hi @starlightsss77, Thank you for sharing your experience! If the task is running but the sound isn’t playing, there might be a few issues causing this. Let’s go through some troubleshooting steps: ### 1. **Verify the VBScript File** - Double-click the **LogonSound.vbs** file manually. Does the sound play? - **If it plays**: The script is fine, and the issue might be with the task configuration. - **If it doesn’t play**: Double-check the script for errors and ensure the file paths and file names match. ### 2 **Check the Sound File** - Confirm that the **LogonSound.wav** file exists in the correct directory (e.g., **C:\Windows\Media**) and plays correctly using a media player. - Ensure the `.wav` file is in a standard format. You can use tools like [Audacity](www.audacityteam.org/) to re-save it in an uncompressed PCM `.wav` format. ### 3 **Move the `.wav` File to Another Location** If the issue persists, try moving the `.wav` file to a simpler directory, such as **C:\Media**, and update the script accordingly: oSpFileStream.Open "C:\Media\LogonSound.wav" ### 4. **Task Scheduler Configuration** - In the **Actions** tab of the Task Scheduler, verify the program/script field contains: wscript.exe - Ensure the **Add arguments** field has the full path to your script, for example: "C:\Windows\Media\LogonSound.vbs" - Check that the task is configured to run for **all users** if needed and is set to **Run whether user is logged on or not**. ### 5. **Permissions Issue** - Since the script is running at logon, it may require elevated permissions. - Right-click the **LogonSound.vbs** file, go to **Properties**, and ensure it’s not blocked. - For the task, ensure the **Run with highest privileges** checkbox is selected in the **General** tab. ### 6. **Test the Task Manually** - In Task Scheduler, right-click your task and select **Run**. If the sound plays, the task is working. If not, revisit the above steps. Let me know if these steps help resolve the issue or if you’re still facing difficulties. I’ll be happy to assist further! 😊

@cnatt yes I tried everything...when I got run on task scheduler it's running...but when I restart then login the sound doesn't play....

Hi @starlightsss77, Thank you for following up! Since the task runs manually in Task Scheduler but doesn’t play the sound after restarting and logging in, the issue might be related to task execution timing or permissions. Here are some additional things to check: ### 1. **Adjust Task Scheduler Settings** - Open your task in Task Scheduler, go to the **General** tab, and ensure: - The **Run with highest privileges** option is checked. - The task is set to **Run whether user is logged on or not**. - In the **Triggers** tab: - Double-check the trigger is set to **At logon**. - Try adding a small delay by clicking **Edit**, checking **Delay task for**, and setting it to **30 seconds**. ### 2. **Check File Accessibility at Logon** - Ensure the `LogonSound.vbs` file and `LogonSound.wav` file are stored in a location accessible at startup, like **C:\Windows\Media**. - Right-click each file, go to **Properties**, and check for the **Unblock** button. If it appears, click it. ### 3. **Verify Account Permissions** - Ensure the task is running under the correct user account. In the **General** tab, check the **When running the task, use the following user account** field. ### 4. **Enable Task History for Debugging** - In Task Scheduler, select your task and click **Enable All Tasks History** in the right pane. - After logging in, check the task history to see if it shows an error or indicates the task was skipped. ### 5. **Event Viewer Logs** - Check the Event Viewer for any related logs under **Windows Logs > Application** or **Task Scheduler (Local)**. Look for any errors that can guide us further. ### 6. **Alternative Approach** If the issue persists, you can test storing the files in a different directory, such as **C:\Media**, and update the script paths accordingly. Sometimes, using a custom location avoids permission-related conflicts. Please try these steps and let me know how it goes. If the issue continues, feel free to share any error messages or logs, and I’ll be happy to assist further! 😊

Hi @starlightsss77, Thank you for your question! If you select Run at startup in the Task Scheduler instead of At logon, it will work, but there’s a key difference: At logon: The task will run each time a user logs in to their account. At startup: The task will run when the system starts up, even before any user logs in. If your goal is to play the logon sound specifically after logging into a user account, then At logon is the correct option. However, if you want the sound to play as soon as the system starts (and possibly before logging in), selecting Run at startup will work for that purpose. Keep in mind: If the sound file or script requires access to user-specific directories, selecting At startup might cause issues because those directories may not be accessible until a user logs in.

You're very welcome! 😊 I'm thrilled to hear that the video solved your update issue after such a long time. Thanks for sharing your experience! 🙌

Hi @freewi11, Thank you for your comment! The error `0x80045003` usually occurs when the VBScript cannot find or access the `.wav` file, or there is an issue with its format. Here are several solutions to help resolve the problem: ### Solution 1: Verify the `.wav` File Path 1. Ensure the **LogonSound.wav** file is located in the **C:\Windows\Media** directory. 2. Double-check that the file path in your script (line 3: `oSpFileStream.Open "C:\Windows\Media\LogonSound.wav"`) matches the exact location of the file, including the file name and case. ### Solution 2: Move the `.wav` File to Another Location If the issue persists, try moving the `.wav` file to a simpler directory, such as **C:\Media**, and update the script accordingly: oSpFileStream.Open "C:\Media\LogonSound.wav" Save the changes and run the script again to test. ### Solution 3: Check the File Format 1. Make sure the file is in a valid **.wav** format. If it’s not or is corrupted, use tools like [Audacity](www.audacityteam.org/) to convert it into a standard `.wav` file. 2. Try testing with a different `.wav` file to confirm if the issue lies with the original file. ### Solution 4: Re-register the SAPI Library If the above steps don’t resolve the issue, the Windows SAPI (Speech API) library may need to be re-registered. Follow these steps: 1. Open Command Prompt as **Administrator**. 2. Run the following command: regsvr32 sapi.dll 3. Restart your computer and test the script again. ### Solution 5: Test the Script After making the changes, double-click the **.vbs** file to ensure it works without errors. If the sound plays, you’re all set! Let me know if this resolves your issue, or feel free to reach out with any additional questions. I’m happy to help! 😊

Thank you so much for your kind words! 🙏 We're thrilled to have you here and really appreciate your support.♥

Hi @ImSniperLmao, If your Windows 11 doesn't show the "Virus & Threat Protection" option, it could be due to a few reasons. Here's how you can troubleshoot: ### 1. **Check if Another Antivirus is Installed** - If you're using a third-party antivirus (like Norton, McAfee, or Avast), it might disable or replace Windows Defender. Check your installed programs in **Settings > Apps > Installed Apps** or in the Control Panel. If you prefer using Windows Defender, you may need to uninstall the third-party antivirus. ### 2. **Ensure Windows Security is Enabled** - Go to **Settings > Privacy & Security > Windows Security** and click **Open Windows Security**. - If you don't see the options, your system might have a configuration issue or a restriction set by your organization. ### 3. **Restore Windows Defender** - Open **PowerShell as Administrator** and run this command to restore Defender: DISM /Online /Cleanup-Image /RestoreHealth - Restart your computer and check if the issue is resolved. ### 4. **Check Group Policy Settings (For Pro/Enterprise Editions)** - Press **Windows + R**, type `gpedit.msc`, and hit Enter. - Navigate to **Computer Configuration > Administrative Templates > Windows Components > Microsoft Defender Antivirus**. - Ensure the policy **Turn off Microsoft Defender Antivirus** is set to **Not Configured**. ### 5. **Reinstall Windows Security** - If none of the above works, you can try reinstalling the Windows Security app using PowerShell: Get-AppxPackage Microsoft.SecHealthUI -AllUsers | Remove-AppxPackage Then reinstall it using: Add-AppxPackage -register "C:\Program Files\WindowsApps\Microsoft.SecHealthUI_10.0.0.0_x64__8wekyb3d8bbwe\AppxManifest.xml" -DisableDevelopmentMode Let me know if any of these steps help, or if you're still having issues. I'll be happy to assist further!

Thank you so much for your comment and support!

Thank you for your question! 😊 The **codes.txt** file is available in two places: 1. The link and code are included in the video description. 2. You can also access it directly through this link: pastebin.com/raw/H01L0f0r Let me know if you need any further assistance!

You're absolutely correct, and as explained at minute 04:13 in the video, if the CPU does not support SSE4.2, the latest version of Windows 11 you can install is 23H2. Attempting to install version 24H2 on such a CPU will result in an unbootable system. Thank you for pointing this out! 😊

Hi @ajoredetobi7987, great question! To achieve this, you can enable the "Fast Startup" feature and make sure Hibernate mode is active. Here’s what to do: 1. **Enable Hibernate Mode:** - Open Command Prompt as an administrator (type “CMD” in the Start menu, right-click it, and choose “Run as administrator”). - Type `powercfg -h on` and press Enter. 2. **Add Hibernate to the Power Menu:** If you don’t see the Hibernate option in your power menu: - Open "Control Panel" > "System and Security" > "Power Options." - Click on "Choose what the power buttons do" from the left panel. - Click "Change settings that are currently unavailable." - Under "Shutdown settings," check the box next to "Hibernate" to enable it. - Click "Save changes." Now, you’ll see the Hibernate option in the power menu! 3. **Use Hibernate Instead of Shut Down:** When you want to turn off your laptop but keep everything as it is, select the "Hibernate" option instead of "Shut Down." This saves the current state of your system (open tabs, apps, etc.) and restores them when you power it back on. 4. **Set Hibernate as the Default Action:** - Go to "Control Panel" > "System and Security" > "Power Options." - Click on "Choose what the power buttons do." - Set the power button or lid close action to "Hibernate" for both battery and plugged-in modes. With these steps, your laptop will return to the exact state you left it. Let me know if you have any more questions! 😊

You're very welcome! 😊 I'm so glad it worked for you. Thanks for your kind words and for taking the time to share your feedback. ❤

Sorry to hear that this method didn’t work for you! I recommend checking **Method 2: Upgrading Windows 11 Using an ISO File**, starting at ****11:25**** in the full video. This alternative approach often resolves issues with the upgrade process. Here’s the link to the video: [kzbin.info/www/bejne/rYa6h5-GjtNllc0](kzbin.info/www/bejne/rYa6h5-GjtNllc0) Feel free to ask if you have any further questions or run into any issues. I’m here to help! 😊 Best regards, The CNATT Channel QA-20241218-02 (This code is used for faster follow-up on your question.)

I completely understand your frustration-it’s incredibly annoying when issues like losing internet connection persist after an update. Unfortunately, you’re not alone, as many users have reported similar problems with the 23H2 update. You could try some troubleshooting steps like updating your network drivers, resetting network settings, or even rolling back the last update if the issue persists. I’ve also shared two tutorials on resetting network settings that might help resolve the issue: 1. **How to Reset Network Settings in Windows 11 using CMD** [kzbin.info/www/bejne/ZnLElJ2GhpqoiaM](kzbin.info/www/bejne/ZnLElJ2GhpqoiaM) 2. **How to Quickly Reset the Network Settings of Windows 11 (Using Windows Settings)** [kzbin.info/www/bejne/lZ7VpK13ms2kqs0](kzbin.info/www/bejne/lZ7VpK13ms2kqs0) If you need guidance with any of these steps, feel free to let me know-I’d be happy to help! Hopefully, Microsoft will release a fix soon to resolve this issue permanently. Best regards, The CNATT Channel QA-20241218-01 (This code is used for faster follow-up on your question.)

You’re very welcome! 🎉 I’m glad to hear that you successfully upgraded your Core i5-6400 PC to 24H2. It’s always great when everything goes smoothly. Thanks for watching and supporting the channel. 😊

Thank you for your comment and for sharing your experience.