Windows Server 2019 grey "X" on folders on LTO
Hi everyone We have just upgraded one of our servers from 2016 to 2019 Std. Since then when I try to copy a file to the LTO, which is directly connected to the server, icons appear with a grey "X" in the bottom left corner. I tried moving the file but the same result appears (when I move it back to the Desktop the "X" disappears). There is no cloud sync of any kind related to this server. Just to be clear, everything worked fine on 2016. Hope someone is able to help. Thank you in advance. Best regards
Possible to recover permanently deleted files windows server 2016?
Hi everyone, I am currently managing a Windows Server 2016 setup and accidentally deleted some important files. Unfortunately, these files are not in the Recycle Bin, which makes me think they’ve been permanently deleted.The server holds critical business data, and recovering these files is a top priority. I have not installed or written any new data to the affected drive to avoid overwriting the lost files. Before diving into third-party tools or professional services, I want to explore any built-in methods or reliable tools recommended by the community forrecovering permanently deleted files on Windows Server 2016.If you've encountered a similar issue or know of any solutions, please share your expertise! Looking forward to your advice. Thanks in advance!
Drivers to install Windows after wiping out partisions
I have two servers (an old physical server and a VM hosted by VMware Workstation) with 3 iSCSI disks each. A previous Linux installation was wiped out using Gparted from both servers. When I try to install Windows Server 2022 I can't select any drive to install Windows and I am requested to load a driver. Where can I find the driver to recognize the disks? What can I do with Gparted or any other tool to make the disks visible by Windows installer? By the way, I can install Linux on both servers without any problem. RegardsWindows Server 2016 on ESXi, two servers solution in case of failure
Hi, I'm facing a problem I still can't find a solution to. Short description below. ESXi virtualization environment has a Windows Server 2016 Datacenter installed. The Server has AD switched on, for the sake of our discussion I'm naming it "contoso.local". There are shared resources on the virtualized server such as shared folders and files, also there is MS SQL server which receives incoming connections from Windows clients (Win10/11). What do I need to achieve? I need to create another virtualized Windows Server 2016 Datacenter or Standard which will be an alternative server that will start offering its services immediately in case of the another server failure. What do I mean by "immediately" here? I mean, the switching procedure/time must be immediate and all the resources such as shared folders or SQL databases must be up-to-date. So, if at 1:00 PM the first server has a failure (disconnected, shut down by mistake etc), the other server must take control of the client machines at 1:05 PM. And as I mention all shared resources and SQL connections must stay the same but on the second server. The users on client machines can't have their work disrupted (any open Word documents in shared foilders intact or financial software connections kept on). I'm aware of the fact that the second server must be a sort of replica that works all the time and receives data from the server so it must be a 1-1 copy of all data that it constantly updates itself with new data coming from the first server. The question is - how can this be done ? I tried Cluster failover, storage replica already but this mechanism didn't work out. I created two disks (logs, data) according to step-by-step instructions but it is still not a solution to the problem. I'll appreciate any advice to my issuewof compression not working on Server 2019, compact /exe:lzx
Hi! Got this oddity where it works on some 2019 but not others. It's volumes that support compression. compact /c .\textfile.txt Compressing files in E:\test\ textfile.txt 80510 : 20480 = 3,9 to 1 [OK] Works. But this doesn't compact /c /exe:lzx .\textfile.txt Compressing files in E:\test\ textfile.txt [ERR] textfile.txt: The file system does not support compression. Found another tool that gives a little bit more / other info. https://github.com/wimbrts/WOF_Compress WofCompress.exe /c:lzx /path:textfile.txt Compression using LZX algorithm Error WOF driver missing! Some more info posted as issue at the authors github. https://github.com/wimbrts/WOF_Compress/issues/1 Anyone got a clue why it works on some server and not others? I've compared the output from fsutil fsinfo ntfsinfo fltmc filters Not working server: NTFS Volume Serial Number : 0x90e6dd9ee6dd84be NTFS Version : 3.1 LFS Version : 2.0 Number Sectors : 0x00000003feeaefff Total Clusters : 0x000000007fdd5dff Free Clusters : 0x000000000b47a437 Total Reserved : 0x000000000000118d Bytes Per Sector : 512 Bytes Per Physical Sector : 4096 Bytes Per Cluster : 4096 Bytes Per FileRecord Segment : 1024 Clusters Per FileRecord Segment : 0 Mft Valid Data Length : 0x000000000a9c0000 Mft Start Lcn : 0x00000000000c0000 Mft2 Start Lcn : 0x0000000000000002 Mft Zone Start : 0x00000000000ca9c0 Mft Zone End : 0x00000000000d71c0 Max Device Trim Extent Count : 0 Max Device Trim Byte Count : 0x0 Max Volume Trim Extent Count : 62 Max Volume Trim Byte Count : 0x40000000 Resource Manager Identifier : A36B7921-4B02-11E3-80B9-10604B92980C fltmc filters Filter Name Num Instances Altitude Frame ------------------------------ ------------- ------------ ----- WdFilter 5 328010 0 storqosflt 0 244000 0 wcifs 0 189900 0 CldFlt 0 180451 0 FileCrypt 0 141100 0 luafv 1 135000 0 npsvctrig 1 46000 0 Wof 1 40700 0 Working server: fsutil fsinfo ntfsinfo NTFS Volume Serial Number : 0x5674e49574e478df NTFS Version : 3.1 LFS Version : 2.0 Number Sectors : 0x000000000fb557ff Total Clusters : 0x0000000001f6aaff Free Clusters : 0x0000000001356a89 Total Reserved : 0x00000000000013ff Bytes Per Sector : 512 Bytes Per Physical Sector : 4096 Bytes Per Cluster : 4096 Bytes Per FileRecord Segment : 1024 Clusters Per FileRecord Segment : 0 Mft Valid Data Length : 0x000000003d880000 Mft Start Lcn : 0x00000000000c0000 Mft2 Start Lcn : 0x0000000000000002 Mft Zone Start : 0x000000000061e7c0 Mft Zone End : 0x0000000000622b20 Max Device Trim Extent Count : 4096 Max Device Trim Byte Count : 0xffffffff Max Volume Trim Extent Count : 62 Max Volume Trim Byte Count : 0x40000000 Resource Manager Identifier : 0F1B4301-B8F1-11EB-BBB6-00155D289A03 fltmc filters Filter Name Num Instances Altitude Frame ------------------------------ ------------- ------------ ----- MsSecFlt 6 385600 0 WdFilter 4 328010 0 storqosflt 0 244000 0 wcifs 0 189900 0 CldFlt 0 180451 0 FileCrypt 0 141100 0 npsvctrig 1 46000 0 Wof 1 40700 0Why can't I run Enable-ClusterS2D more than once per windows installation?
I have been trying to setup this bloody cluster storage spaces direct configuration for over a month and have re-installed everything on the server more than a dozen times. Every time I get to running the command for the first time, it makes some configuration that is not what I want and there is absolutely no way that I can undo the changes or fix them in any way, shape, or form except by completely wiping the server and reinstalling the entire operating system. I have tried to run Disable-ClusterS2D and then re-run the Enable-ClusterS2D and it will hang on "Waiting until all physical disks are reported by clustered storage subsystem". I try to completely detach the entire pool and wipe it manually and reclaim the disks and recreate the pool, and guess what, "Waiting until all physical disks are reported by clustered storage subsystem". I wipe the entire cluster configuration and recreate the cluster from scratch. Did that work? Of course not, "Waiting until all physical disks are reported by clustered storage subsystem". This has happened on both Windows Server 2022 and 2025, Datacenter editions. Why can I not run the command more than once per operating system??? If I need to replace a disk, am I just supposed to wipe the whole operating system??? Isn't this **bleep** thing supposed to be enterprise grade and just work???VM Spanning or Storage Pool
Hello, When creating VMs are you combining disks using Disk Management Spanningor Server Manager Storage Pools? Data usage, random fileserver data Excluded boot OS, this is a basic separate disk. I'm reading that dynamic disk is obsolete and storage pools should be used. But is this relevant for VMs when storage is managed via hardware RAID e.g. SAN, Fibre attached etc Thank you, Leo.
How to manage garbage collection not to disrupt services on web application
Greetings, I need your expertise, to resolve a painful issue regarding Gc process always running on my stand-alone servers causing disruption. I limited my IIS to always run recycle after reaching 20gi of memory consumption, I also set the site to use server gc , but all the time my servers are undergoing Gc which disrupts service. Any solutions over there to get off this nightmare
