Windows 11 Windows 11 Access to other Devices on the same network

[Superbee]

I have tried to fix this with no luck, I'm new to Windows 11 never had any problems with 10, i have a TV box Q-Box running Linux all i had to do is create shortcut with IP address to access everything with File Explorer on it transfer files and so on, Windows 11 won't let me have access to it at all comes up with Windows Security Box wants me to log-in?

 

[ChatGPT]

Hi Superbee — welcome. I didn’t receive any attachments with your post (if you tried to upload something, please try again).
Short answer: Windows 11 is asking for credentials because it’s blocking “guest/insecure” SMB access by default and/or is expecting a valid Samba user/password from your Q‑Box. I’ll give quick checks and fixes (safe → simple → more advanced), plus undo notes.
Before you start

• Make sure your PC’s network profile is set to Private (Settings > Network & internet > Properties > Private).
• Make sure the Q‑Box is on the same IP subnet and you can ping it from the PC: open Command Prompt and run:
  netsh interface ipv4 show addresses
  ping <Q-Box-IP>

If ping fails, stop here and tell me the IP and ping output.
Step 1 — quick attempt to connect and add credentials

1. In File Explorer address bar type:
   \<Q-Box-IP>\
   (example: \192.168.1.55)
   • If a Windows Security box appears, note whether it offers username/password fields or a message about “network credentials”.
2. If it asks for credentials, click “More choices” → “Use a different account” and try:
   • If your Q‑Box uses a username: enter username and password used on the Q‑Box Samba share.
   • If the share is supposed to be anonymous/guest: try “Guest” or just leave the username blank (some configs need username guest and blank password).
3. If that fails, add a saved credential:
   • Open Control Panel > Credential Manager > Windows Credentials > Add a Windows credential
     • Internet or network address: <Q-Box-IP>
     • Username: <samba-username> (or guest)
     • Password: <password>
   • Then retry \<Q-Box-IP>\ in File Explorer.

Step 2 — map the share (shows if Windows accepts credentials)
Open an elevated Command Prompt and run:

• To map a share with username/password:
  net use Z: \<Q-Box-IP>\<share> /user:<username> <password> /persistent:yes
• If mapping succeeds you’ll see Z: in File Explorer.

Step 3 — Windows 11 blocks “insecure guest” by default (if your box is guest-only)
If your Q‑Box’s Samba share allows only guest access (no username/password), Windows 11 usually blocks this. Two options:
A — Enable insecure guest auth (Windows side) — less secure, quick test

• Recommended only for home/lab networks, not on public networks.

PowerShell (run as Administrator):

• Enable guest auth:
  Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters" -Name "AllowInsecureGuestAuth" -Value 1 -Type DWord -Force
• Restart the PC (or stop/start the Workstation service).

To undo:
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters" -Name "AllowInsecureGuestAuth" -Value 0 -Type DWord -Force
B — Better option: configure Samba on the Q‑Box to require a username/password

• On the Q‑Box edit /etc/samba/smb.conf for the share and ensure the share has a valid user and password, or enable map to guest only if you must. Example share stanza for a password-protected share:
  [shared]
  path = /path/to/share
  valid users = youruser
  read only = no
• Add a samba user/password with:
  sudo smbpasswd -a youruser
• After that, use that username/password from Windows credentials.

Step 4 — SMB protocol version (only if Q‑Box uses very old SMBv1)
If your Q‑Box or its Samba install requires SMBv1 (rare but possible on old devices), you can temporarily enable SMBv1 on Windows 11 — this is a security risk and should be avoided unless necessary.
PowerShell (Admin) to enable SMB1:
Enable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol -All
To disable again:
Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol
Step 5 — If you want me to check the Q‑Box Samba config
Tell me:

• The model/name of the Q‑Box and OS version (or paste the relevant smb.conf share stanza).
• The exact text of the Windows Security box or any error message.
• Whether you used to connect with a username or you connected as anonymous/guest on Windows 10.

Common things that cause the Windows Security prompt and failure

• Samba requires credentials but you’re trying to connect as guest.
• Windows 11 blocks insecure/guest SMB by default.
• Wrong domain/workgroup prefix — try entering credentials as WORKGROUP\username or <Q-Box-Hostname>\username.
• Authentication protocol mismatch (SMB1 vs SMB2/3).

If you want, try these and tell me the exact message shown in the Windows Security box (and whether it has options like “More choices”), plus the Q‑Box IP and share name — I’ll give exact commands and the safest fix for your setup.

 

[Superbee]

ok with what you gave me here i tried most of it with no luck, so i messed with the q-box on samba turn on name and password, and boom I'm in, i want to thank you

should i start a new thread for my next problem or just add it here?
Memory Integrity
igdkmd64.sys

 

[ChatGPT]

Great — glad the Samba fix worked and you got access. You can keep the new problem in this same thread if you like, but because Memory Integrity / igdkmd64.sys is a different topic it’s usually clearer to start a new thread (helps others find the solution later). Up to you — either is fine.
Short explanation (what’s happening)

• igdkmd64.sys is the Intel graphics kernel‑mode driver. When Windows’ Memory Integrity (HVCI / Core isolation) is turned on it will refuse to load drivers that are unsigned, old, or otherwise incompatible — that can show igdkmd64.sys as the blocker or cause BSODs.
• The usual fix is to update or replace the Intel graphics driver (or remove the offending driver and install a compatible one); tools like Display Driver Uninstaller (DDU) are commonly recommended to fully remove a bad driver before reinstalling.
• Memory Integrity is a useful security hardening feature (HVCI) and it’s worth enabling — but you must resolve incompatible drivers first.

What I recommend — step‑by‑step
Make a restore point or full backup before changing drivers.
1) Check the Memory Integrity / incompatible driver message

• Open Windows Security → Device security → Core isolation details. See if igdkmd64.sys (or “Intel Graphics …”) is listed as incompatible. If it is, that’s the exact blocker.

2) Check current Intel driver info

• Device Manager → Display adapters → (Intel adapter) → Properties → Driver tab. Note Driver Provider, Date and Version.

3) Update the driver (best first step)

• Preferred: get the latest Intel driver from your PC maker (Dell/HP/Lenovo/etc. — OEM drivers are usually the safest. If none available, get the Intel driver (Intel Driver & Support Assistant or manual download). After installing, reboot and re-check Memory Integrity. Many forum fixes point to updating the Intel driver as the cure.

4) If updating doesn’t work — clean uninstall + reinstall

• Boot into Safe Mode.
• Run Display Driver Uninstaller (DDU) to remove existing Intel graphics drivers (safe to follow DDU instructions). After DDU and reboot, install the fresh Intel/OEM driver and reboot. This approach is commonly recommended when the driver itself is corrupted or not updating cleanly.

5) If no compatible driver is available

• Temporarily install the Microsoft Basic Display Adapter so the system runs without the problematic Intel driver: Device Manager → Display adapter → Update driver → Browse my computer → Let me pick from a list → Microsoft Basic Display Adapter. Then try enabling Memory Integrity. This reduces graphics features but can show whether the Intel driver is the issue.

6) If you get BSODs pointing to igdkmd64.sys

• Boot Safe Mode, run DDU, then either install OEM/Intel driver or use Microsoft Basic Display Adapter. If you have a separate discrete GPU (NVIDIA/AMD) plus Intel integrated, ensure drivers don’t conflict — sometimes disabling the integrated adapter in BIOS (if you don’t need it) is an option.

7) Re-enable Memory Integrity

• After the driver is replaced/updated and you reboot, go back to Windows Security → Device security → Core isolation details and toggle Memory Integrity ON. Reboot when prompted.

What I need from you if the above doesn’t fix it

• Tell me what you see in Core isolation details (is igdkmd64.sys listed?.
• Windows version and build (Settings → System → About).
• The laptop/PC model and whether you have Intel integrated + discrete GPU (e.g., Intel HD + NVIDIA).
• If you have a minidump or crash log (files you uploaded), say which file(s) are the dumps and I can analyze them — if you want me to analyze, I’ll ask you to confirm the dump names so I can pull them.

Quick safety notes

• Avoid enabling SMB-style insecure workarounds here — for drivers, prefer updating or clean reinstall.
• If you use DDU, follow its Safe Mode instructions and reinstall drivers immediately after reboot.

If you want, I can walk you through the exact steps for:

• Using Device Manager to update/roll back drivers, or
• Running DDU safely, or
• Installing an OEM/Intel driver step‑by‑step.

Which would you prefer, and do you want to continue here or open a new thread?