Windows smb client and Zone.Identifier (WSL) authentication problem
hi together, we have an import process which import data from a csv file from a nas. I have change the nas server (from old to new server) and activate smb logging. Now i can see the following problems. We have on the nas a local user for application access and on the windows client side a other local user too (different names). Client machine is windows version 1809 build 17763.6414 (windows 10 enterprise ltsc). 1. problem - wrong Authentication Data for writing "Zone.Identifier" We configred the authentication data in the import process and the process used this data for access to the csv files. But it looks like that windows meta data process don't use this authentication data. I saw in tcpdump pcap file 4 smb sessions. First and secound smb sessions use the authentication data for the access to the 2 csv files. The third smb session use no authentication data. so that the access don't work. Whatevery windows in the third smd session will doing. The fourth smd session use a mix of source maschine name und destination user, which is not correct. I add read/write access for everbody, so that i can see, what is doing in the fourth session. Windows will writing/access to the Zone.Identifier file. 1. smb session: User: <nas>.<domain>\<nas_user> 2. smb session: User: <nas>.<domain>\<nas_user> 3. smb session: User: \ 4. smb session: User: <client machine name>\<nas_user> 2. problem - ignore "Do not preserve zone information in file attachments" setting now i activate this setting, so preventing writing of this kind of informations/files. But the windows client ignoring it. I have reboot the windows client and repeat the import process and windows tried to writing the zone information again. I change the setting about the following way. admin: gpedit.msc -> User Configuration > Administrative Templates > Windows Components > Attachment Manager and than enable the policy named "Do not preserve zone information in file attachments". Is this a know issue or hae sameone any idea? I would prevent the 3. and 4. smd session, so the access for the meta data proccesses. best regards Christian Voigt
WSL Issue "The system cannot find the file specified"
Can any one help me to solve the issue PS C:\Users\username> wsl --install The system cannot find the file specified. PS C:\Users\username> wsl --list --verbose The system cannot find the file specified. PS C:\Users\username> wsl --shutdown >> The system cannot find the file specified. PS C:\Users\username> <distro-name> Installing, this may take a few minutes... WslRegisterDistribution failed with error: 0x80070003 Error: 0x80070003 The system cannot find the path specified. Press any key to continue...WSL2 now available on Windows Server 2022
Hello folks! If you’re one of those Devs/ITPros using the Windows Subsystem for Linux (WSL) you know how useful and powerful it can be. We announced during Microsoft Build last week that WSL2 will be broadly available in June. But I could not wait. Here’s how I installed it. It’s pretty simple. Check it out!WSL won't install after upgrading to 24H2？
I am running the current Dev Windows 11 build. Ever since I upgraded from 23H2 to 24H2 I've been unable to get WSL to work. When I run "wsl.exe" I get the following message: Downloading: Windows Subsystem for Linux 2.1.5 Installing: Windows Subsystem for Linux 2.1.5 Catastrophic failure
25201.1000 is failing with error 0xc1900101
**UPDATE** I orginally reported it as below, but it turns out after setting my clock back and re-trying the installation, that 25201.1000 is failing with error 0xc1900101. 25201.1 Insider Update Immediately Expired: Broken WSL According to my update history, last night I had the Windows 11 Preview 25201.1 applied to my machine, and this morning WSL was broken and I'm constantly nagged by a message "This build of Windows will expire soon". However when I look at winver, it shows that I have Version 22H2 25169.1. I'm unable to fetch any new updates, and Windows Update won't apply the latest antivirus patch because it says there's a problem with my PC system time (there is not). I use WSL every day and now both WSL and subsequently Docker are broken because of this... it's rather infuriating. Any suggestions on what I can do from here?Feature Request to integrate WSLG with Multiple Desktops by integrating RDP with Multiple Desktops
It would be incredibly convenient if windows allowed apps to integrate with the multiple desktops/task view feature. The idea that sparked this for me was that it would be nice if I could create a new desktop for my wslg installation of ubuntu. And instead of creating a mini RDP window when launching apps from the start menu, it would check if I had an ubuntu desktop open and would create it there instead (Also preferences as a part of the windows settings app for this would be nice). Also it would be great if I could use the multiple desktops feature to switch to one of my remote computers. Additionally having the start menu shortcuts for wslg apps in a folder feels incredibly cumbersome and directly against the Win 11 ethos. Perhaps it would be better to find a better, more adaptable solution to this because it could also be applicable to android apps whenever that feature comes out. Perhaps this feature could be expanded to something like a Rich RDP where you could even launch apps on remote computers which you are not already connected to simply by clicking it in the start menu. While im on a roll here, I'm perplexed as to why Microsoft's clean new apps like console and RDP are not shipped as default programs with windows 11. I'm looking for an internship/full time pos too, are there any managers on the windows dev team that I could send my resume? lol
