New
#40
Hi there
Don't get too carried away with this build --if you need to access files FROM this build while logged on to another system e.g any NAS type servers (Non Windows) there's file access problems -- sftp for example doesn't work (FROM the other system TO this windows build) because openssh server fails on install.
Doesn't seem to matter on how you set the insider settings either --same result.
Either use build 331 (working) or wait till this build is updated again.
The 21H1 build works OK too.
Cheers
jimbo
What gives with 20H2 and Sleep mode?
Intermittently when I put the computer to sleep the monitor powers down as do the USB's but the power supply stays on. Will not wake with keyboard or mouse. Never happened before 20H2. I had to remove the update because Sleep mode is active 12 hours a day every day and can't afford computer locking up like this.
I've Clean Installed 20H2 19042.330 twice now to a Hyper-V VM and both time I end up with a problem when I boot or restart. I end up at this screen, the mouse and keyboard are live but do nothing. I can click on Ease of Access or Power and they work. I originally posted in the 2004 thread as I thought that was a Host problem but it turn out not to be. More info, including some screen captures in the thread there:
KB4567523 Cumulative Update Windows 10 v2004 build 19041.331 - June 18
This build is starting to grow a long white beard. If MS is still sticking to its announced June & December feature finalize schedule, 20H2 should be finished except for fixes it clearly needs. But enough is wrong for them to be pumping out upgraded betas. Maybe soon.
Hi folks
@larc919
This build has about as much relevance to Windows as the old "Piltdown man Scandal" to Human evolution
Piltdown Man - Wikipedia
Networking -- MEGA Fail
OpenSSH server Fail (means you cant retrieve files from this build via safe fast encrypted protocols like sftp from remote servers / laptops etc.
Stick with builds 329 and 331 which actually work !!!!
Cheers
jimbo
The 20H2 19042.330 build is the first I've had real problems with in a long time. So far only a Hyper-V VM problem though so may be fine (for me) when installed in real hardware.