New
#30
Hi there
surely better to fix any ongoing problems with the file system (NTFS) than waste time defragging (should never be needed these days even on older "spinners" and certainly not on SSD's) and using TRIM.
The NTFS system is quite ancient by todays computing standards -- especially now quite a lot of people use large capacity HDD's (> several TB) or even things like aggregating HDD's / RAID 0 etc so sizes of over 20 - 30 TB aren't that uncommon any more.
If the File system needs updating that's the area to fix. I don't think some of the newer Linux file systems need to defrag etc -- e.g XFS, EXT4, BRTFS etc. They also have excellent journaling facilities too so repair isn't always a problem if they get broken.
Cheers
jimbo
Hi folks
This build IMO seems the best of all the "Insider" and fast / slow rings so far !!
Networking OK both INBOUND and OUTBOUND to and from NAS (non Windows / Linux) servers (I had problem with the fast ring build -- W10 would only accept INBOUND connections from other Windows machines).
(Bottom image the Windows machine is the right hand pane -- no problems accessing from a NAS using filezilla).
Language menus fixed properly
No expiration date
BTW the new edge looks a lot better than the old one -- new icon as well (for those that are concerned with icons !!) -- Still no MENU or decent toolbars for bookmarks unlike firefox though. Icon is the 3rd one on the icon list on the task bar.
System also seems slicker than previous (insider) builds probably borne out by CPU load on the VM I'm running. On previous build the graph of CPU load showed at least double the current one -- also when running only 1 VM at a time.
Running as a VM -- CPU load a LOT less than previous builds --running same workload as previous VM's as well. You can see from the manage VM's screen. (VM manager -- LIBVIRT's GUI).
Cheers
jimbo
Hi folks
can anyone install openssh server on this build
I get some rubbish about failed --see Windows insider settings -- no errors there :
This is actually a show stopper for me on this build if I can't get this installed -- I run a job on a NAS (Linux) based server to send a file via sftp to windows clients and then I need the windows clients to run a backup and send the file back to the NAS server. Script works perfectly until this build of Windows -- one part of the process needs Windows to act as the OPENSSH server. The client bit is fine.
Clearer indication of the problem.
Here I'm on a Linux NAS server with a GUI
Connect to a Windows 20H2 machine via SAMBA is OK but that's not what I want.
Connect via OPENSSH fails (filezilla) and sftp
easier to show in the GUI
cheers
jimbo
Last edited by jimbo45; 22 Jun 2020 at 03:20. Reason: added screenshot sftp and samba
Does this Beta build have the desktop watermark and expiry date?