Sound not working and also unknown usb devices with surge issue

Hello rajuRoshan,
It sounds like you're experiencing a frustrating combination of audio and USB issues after a fresh Windows install on your Lenovo M73 workstation. Let's break this down step by step to find some solutions.

Sound Not Working​

1. Driver Installation: It's crucial to ensure that all the necessary drivers are installed. Go to the Device Manager:
   • Press Win + X and select Device Manager.
   • Expand Sound, video and game controllers.
   • If there's a yellow exclamation mark on your audio device, you'll need to install or update the driver. You can download the latest audio driver directly from the Lenovo support website here.
2. Audio Services: Ensure that your audio services are running:
   • Press Win + R, type services.msc, and press Enter.
   • Find the Windows Audio service and ensure it’s running. If not, right-click and select Start.
3. Playback Devices: Right-click on the sound icon in the system tray and select Playback devices. Ensure that your internal speaker and headphone are set as the default device. If they're not showing up, it’s likely a driver issue.

USB Issues​

1. Power Surge and Unknown Device: The power surge message often indicates a problem with the USB port or connected devices. Since you're using a PS/2 keyboard and mouse, try the following:
   • Temporarily remove all USB devices and check if the surge message persists.
   • Check the USB connections and ports for any visible damage or debris.
2. Disabling USB 3.0: You noted that disabling the USB 3.0 root hub from Device Manager alleviates the issues with USB. This should be a temporary fix. You might want to consider:
   • Updating the USB 3.0 drivers, which can also be found on the Lenovo support website.
   • Checking for motherboards firmware updates (BIOS), which can sometimes resolve hardware compatibility issues.
3. USB Settings in BIOS: Restart your computer and enter the BIOS setup (usually by pressing F1, F2, or Delete during startup). Look for USB settings and ensure they are correctly set. Sometimes, enabling or disabling legacy USB support can resolve these issues.

Summary​

• Make sure to update your drivers for both audio and USB functions.
• Verify the status of the audio service.
• Check USB ports and connections for physical issues.
• Consider potential firmware updates for the motherboard.

If symptoms persist even after trying the above solutions, please let me know, and we can explore more advanced troubleshooting steps. Good luck!

nah..
sound still didn't work still show no output devices even though i have internal speakers.. window services are running..
Usb issue still persist.. even after bios legacy changes...

You can update or reinstall the audio drivers. You can also download the latest drivers from the Lenovo support website. Make sure to check the playback devices by right-clicking the sound icon in the taskbar and see if your internal speaker or headphones are listed; set them as the default if they are. Running the "Playing Audio" troubleshooter in Settings can help identify and fix problems too.

For the USB issues, check Device Manager for any problems with USB controllers and update the drivers if necessary. Disable power saving for USB Root Hubs by going into their properties in Device Manager. Look for BIOS updates from Lenovo, as these can resolve hardware compatibility issues. If disabling the USB 3.0 root solves some problems, you can keep it that way, but be aware it might limit the speeds of USB 2.0 devices.

It appears you're tackling dual boot and bootloader errors with the rather infamous winload.efi issue. The provided instructions from the post cover a number of key steps to troubleshoot and resolve the matter. Let me elaborate and clarify a couple of points to ensure a thorough response.

---

Winload.efi Error: Detailed Explanation & Solution​

When encountering a missing or corrupted /Windows/System32/winload.efi error, it often indicates issues with:

1. Boot Configuration Data (BCD) corruption.
2. EFI partition errors.
3. Conflict between multiple OS installations.

Step-by-Step Approach:​

1. Fix Bootloader Configuration
   • Commands like bootrec /fixmbr, bootrec /rebuildbcd, etc., mentioned in the solution are valid and detail a strong foundational starting point.
     • Focus on bootrec /rebuildbcd as it specifically rebuilds the boot configuration for finding OS installations.
   • If skipping this step, the dual boot OS may not boot correctly once restored.
2. Verify EFI Partition Health
   • The diskpart commands are essential to checking mapping issues or damaged files in the EFI partition. Ensuring the partition is assigned a letter allows you to:
     • Run a filesystem integrity check (chkdsk Z: /f).
     • Investigate or even manually repair the contents of /EFI/Microsoft/Boot.
3. Repair System Files
   • sfc /scannow along with DISM ensures system integrity.
   • The combination of DISM's RestoreHealth option and SFC makes it highly effective at resolving misplaced or corrupted system files.
4. Dual Boot Reconfiguration
   • After repairing the main OS issues, reconfiguring the dual boot order is critical.
     • Tools such as EasyBCD simplify the process for users who aren't well-versed with bcdedit.
   • Use bcdedit to add entries for both Windows installations.
5. Advanced Tools
   • If all steps fail, reconstruct the boot entry from scratch using a Windows installation media:
     1. Boot with the USB/DVD and select Repair your computer.
     2. Navigate to Troubleshoot > Advanced Options > Command Prompt to execute boot repair commands.
   • Test booting into BIOS/UEFI to confirm both OSes are listed.
6. Backups and Precautions
   • Always back up the existing BCD configuration (bcdedit /export C:\BackupBCD) before making changes.

---

Additional Notes:​

• EFI Partition Visibility:
  If the system has multiple OS's, ensure no conflicting entries remain in /EFI/BOOT or /EFI/Microsoft/Boot.
• File Recovery:
  If winload.efi is missing, it can be manually restored from a working Windows 11 installation or extracted from the installed Windows image.
• Common Dual Boot Conflict:
  Restoring one installation without carefully controlling partition usage can lead to another OS being rendered unbootable. This occurs because both systems commonly access the same EFI directory.

---

If you're running into specific errors while following these steps, feel free to elaborate, and I'll help you further! Are there any edge cases or challenges you're noticing while troubleshooting?