found this on ASUS's website and found it very interesting and i hope the fixes help you all out there as M$ just makes the job harder.
If you cannot use SMB in Windows 11, please refer to the following solutions and choose one of them to set up:
Note: The following methods may reduce system security, so they are recommended only in trusted network environments.
Ｍethod 1. Enable insecure guest logons:
a. Using the Registry Editor:
a1. Type and search [registry editor] in the Windows search bar, then click [Open].
a2. Navigate to [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Win dows\LanmanWorkstation].
If [LanmanWorkstation] does not exist, right-click on [Microsoft], select [New] > [Key], and name it [LanmanWorkstation].
a3. Right-click on [LanmanWorkstation], select [New] > [DWORD (32-bit) Value], and name it [AllowInsecureGuestAuth].
a4. Right-click on [AllowInsecureGuestAuth], select [Modify], set the Value data to 1, then click [OK].
b. Using the Local Group Policy Editor:
b1. Press [Win] + [R] key on the keyboard, type [gpedit.msc], then click [OK].
b2. Navigate to [Computer Configuration] > [Administrative Templates] > [Network] > [Lanman Workstation].
b3. In the right pane, right-click on [Enable insecure guest logons], select [Edit],
b4. Select Enabled, then click [OK].
Ｍethod 2. Disable SMB Signing Requirement:
a. Using the Registry Editor:
a1. Type and search [registry editor] in the Windows search bar, then click [Open].
a2. Navigate to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\LanmanWorkstation\Parameters\RequireSecuritySig nature].
If [RequireSecuritySignature] does not exist, right-click on [Parameters], select [New] > [DWORD (32-bit) Value], and name it [RequireSecuritySignature].
a3. Right-click on [RequireSecuritySignature], select [Modify], set the Value data to 0, then click [OK].
b. Using Windows PowerShell：
b1. Type and search [Windows PowerShell] in the Windows search bar, open [Windows PowerShell] as Administrator.
b2. Enter the following command and press Enter on the keyboard.
Please refer to Microsoft Official Website Information
Group Policy
PowerShell
If you cannot use SMB in Windows 11, please refer to the following solutions and choose one of them to set up:
Note: The following methods may reduce system security, so they are recommended only in trusted network environments.
Ｍethod 1. Enable insecure guest logons:
a. Using the Registry Editor:
a1. Type and search [registry editor] in the Windows search bar, then click [Open].
a2. Navigate to [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Win dows\LanmanWorkstation].
If [LanmanWorkstation] does not exist, right-click on [Microsoft], select [New] > [Key], and name it [LanmanWorkstation].
a3. Right-click on [LanmanWorkstation], select [New] > [DWORD (32-bit) Value], and name it [AllowInsecureGuestAuth].
a4. Right-click on [AllowInsecureGuestAuth], select [Modify], set the Value data to 1, then click [OK].
b. Using the Local Group Policy Editor:
b1. Press [Win] + [R] key on the keyboard, type [gpedit.msc], then click [OK].
b2. Navigate to [Computer Configuration] > [Administrative Templates] > [Network] > [Lanman Workstation].
b3. In the right pane, right-click on [Enable insecure guest logons], select [Edit],
b4. Select Enabled, then click [OK].
Ｍethod 2. Disable SMB Signing Requirement:
a. Using the Registry Editor:
a1. Type and search [registry editor] in the Windows search bar, then click [Open].
a2. Navigate to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\LanmanWorkstation\Parameters\RequireSecuritySig nature].
If [RequireSecuritySignature] does not exist, right-click on [Parameters], select [New] > [DWORD (32-bit) Value], and name it [RequireSecuritySignature].
a3. Right-click on [RequireSecuritySignature], select [Modify], set the Value data to 0, then click [OK].
b. Using Windows PowerShell：
b1. Type and search [Windows PowerShell] in the Windows search bar, open [Windows PowerShell] as Administrator.
b2. Enter the following command and press Enter on the keyboard.
- [*=1]Set-SmbClientConfiguration -RequireSecuritySignature $false
Please refer to Microsoft Official Website Information
Group Policy
PowerShell
Comment