Hi there
Working fine
Other Windows versions (the insider ones) no longer connect seamlessly to non Windows NAS systems via browse network but seem to require specific IP address to connect so that's a bummer.
This version working fine. (NAS systems can connect TO windows but I need Windows TO NAS) -- so newer (insider versions) have something changed --even SMB1 enabling fails to fix problem --- this release though is still working.
Cheers
jimbo
Last one of my machines to update and it turned into a cluster. The update seemed fine and after initial check out, I decided to reconnect both my HDD data drives. (I just do C: when updating) Machine would not start, no lights etc. disconnected both HDD and it would start again. Connected my hatachi 1tb drive, it would start. Disconnected it and connected my WD 2tb, no start. Connected the WD externally thru usb adapter, still no start. Removed the usb connected WD HDD and it started. After login etc, reconnected the WD via usb. It appeared with explorer as if nothing was wrong. Checked the disk, no errors except every file I tried to look at was protected. Checked protection status, every thing was checked for all users. Bios checked for the SSD as primary on boot up.
Went on to the internet to check some things, no connection to the internet. SFC /scannow was error free, malware bytes etc. no detections. Removed the WD HDD, restart and internet returns. WT. ?
Waiting till morning to go at it again. Suggestions appreciated.
Last edited by meebers; 16 Apr 2020 at 08:50.
Updated on my RP machine with no problems.
Windows defender stops working when I install this update on both my machines. Removing the update fixes the issue. This is what I get in event viewer over and over when this update is installed "The Windows Defender Antivirus Service service terminated with the following error: General access denied error"
Hello
My windows defender antivirus has started having errors that stop working, stops and cannot be restarted, unless you start it from services.msc. Yesterday the antivirus was working fine, today I have updated to April 14, 2020 — KB4549951 cumulative update.
I think that i have located the source of the error and it consists of the antivirus stopping when it tries to scan any file whose name is like this:
filename..ext
For example, filename..txt
If you scan filename.txt or filename...txt it does not produce any error, it is only when the file name ends with a point before the file extension.
From what I can tell it seems that starting the windows defender service from services then quickly updating it also fixes the problem. Windows defender doesn't seem to stop working anymore.
Quote
