Windows 10 Insider Preview Build 20175.1000 (rs_prerelease) - July 22 Insider

Page 15 of 17 FirstFirst ... 51314151617 LastLast

  1. Posts : 46,504
    Windows 10 Home 64bit 21H1 and insider builds
       #140

    linw said:
    Unfair to say no problems with SMB1 when MS are strongly advising to disable it for security reasons. I have disabled SMB1 now and have to rely on mapping the NAS.
    Fair point. I wonder just how much a risk it is though.
      My Computer


  2. Posts : 1,936
    win 10 Insider
       #141

    BUT, I too would like to see my NAS show as with SMB1!!
      My Computers


  3. Posts : 46,504
    Windows 10 Home 64bit 21H1 and insider builds
       #142

    linw said:
    BUT, I too would like to see my NAS show as with SMB1!!
    Well I'm going to keep it for the moment anyway. MS could do something about it but I'm not holding my breath.
      My Computer


  4. Posts : 11,172
    Windows / Linux : Arch Linux
       #143

    linw said:
    BUT, I too would like to see my NAS show as with SMB1!!
    @linw
    @kado897

    Agreed !!

    I think a lot of the so called "I.T Security" experts these days are crying Wolf far too much --probably to save their jobs -- OK at national / International / Business levels security is incredibly important -- but at HOME levels assuming you have WD set up and running properly -- very few people get any sort of Virus these days -- that's so last century trying to infect a Mom and pop's computer -- Scamming is the real name of the game these days on home systems and that doesn't get prevented by any amount of Software --the only way you could get a machine to prevent scamming is by incredibly sophisticated A.I and we are probably years away from reaching that level.

    Why should people have to attempt to re-set NAS boxes (if they are running any sort of Linux OS on them they are pretty safe anyway) just because some "Honcho" in a company says -- it's unsafe to still use SMB1 -- without giving any sensible reasons why home (and I repeat HOME) uses should abandon it.

    Most people would have a lot of trouble fiddling around with Linux networking systems on NAS boxes if they had to do this !!!

    Just look at the posts on this Forum alone on Networking -- and we assume most users here are far more computer literate than the average -- I'd hate to fiddle around on a Linux Forum with people who suddenly find they can't access their NAS systems (and some NAS systems are still proprietary e.g QNAP where users have almost zero chance to re-configure them any way).

    A sensible timely transition --OK - some of these boxes and TV's last for years !! -- just look how Windows still supported for X86 systems -- not sure how long ago the last X86 model computer or CPU was sold !!!

    Cheers
    jimbo
      My Computer


  5. Posts : 1,936
    win 10 Insider
       #144

    Yes, jimbo, I do agree with you. I checked the SMB ver of my WD NAS and it was supposed to be able to cope with SMB3 but still no go.

    Weird why we get no info from MS. Makes you wonder why we bother. Bit like mushrooms - fed shlt and kept in the dark!

    But, I will keep going!
      My Computers


  6. Posts : 11,172
    Windows / Linux : Arch Linux
       #145

    linw said:
    Yes, jimbo, I do agree with you. I checked the SMB ver of my WD NAS and it was supposed to be able to cope with SMB3 but still no go.

    Weird why we get no info from MS. Makes you wonder why we bother. Bit like mushrooms - fed shlt and kept in the dark!

    But, I will keep going!
    Hi there @linw

    If you can get into the SAMBA config file --it's normally found in Linux systems in /etc/samba/samba.conf then the default is usually SMB1 on older boxes.

    To change newer ones --- to force SMB1 set this line in the global
    section [global]
    min protocol = NT1

    change to SMB2/SMB3 for other levels of SMB -- then restart the NAS server or from command line if you can get into it as root type systemctl restart smb nmb (2 services -- on some boxes it will be smbd nmbd)

    This doesn't always achieve the right result -- I was trying latest version of Kodi on an amazon firestick to access my NAS files (multi-media) or another Windows box on a remote TV -- the KODI program had a section for security level where you could set the level (previous version 17.6 only works with SMB1). It didn't work of course and until I reset back to "Legacy" I had no no access on either Linux NAS or Windows box from the amazon fire stick which I plug into remote TV.

    Cheers
    jimbo
      My Computer


  7. Posts : 629
    windows 10
       #146

    downloaded and installed and so far no problems
      My Computer


  8. Posts : 29,075
    Windows 10 21H1 Build 19043.1023
       #147

    martyfelker said:
    I don't have a NAS and have not experienced a problem with an AMD (with the exception of a Blue Screen which I posted - the installation continued normally after M$ got their info and interestingly never recurred.) I completely trust @jimbo45's take on things 99% of the time - nobody - not even me - is right 100%. Blunder's like malformed warnings about AMD - from what we used to call Wintel no less - should not be happening on ALPHA's. Nobody testing with AMD could install this build or just continued after small glitches like a blue screen? Unlikely IMHO.
    Actually, Marty, I downloaded, mounted, and did a repair install of Build 20175, saving my personal settings and files, without issue. This on my AMD Ryzen 5 system.
      My Computer


  9. Posts : 17,831
    Windows 10
       #148

    Windows 10 Insider Preview Build 20175.1000 (rs_prerelease) - July 22-000793.png

    ........................

    ........................

    ........................

    ........................

    ........................
      My Computer


  10. Posts : 26
    Windows.8.1, windows10.9860
       #149

    Code:
    C:\WINDOWS\system32>sfc /scannow
    
    Beginning system scan.  This process will take some time.
    
    
    There is a system repair pending which requires reboot to complete.  Restart
    Windows and run sfc again.
    
    C:\WINDOWS\system32>
    Reboot doesn't help, the same result after reboot.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 02:17.
Find Us




Windows 10 Forums