Show Posts
1
Tweaking.com Support & Help / Re: WR v4.7.1 fixed Win 10 start menu, etc. but can't re-connect to SMBv1 Server
« on: December 30, 2019, 06:09:26 pm »
Tom, Thank you for such quick response!
Before I ran WR, I tried a restore point (from 12/17/19, and have only 1 earlier one that I could try now?) ran sfc /scannow, then malwarebytes and rkill & rebooted. No reported errors, rootkits, etc. - but I did not try "dism /restorehealth" . Then I ran WR v4.7.1 fixed which fixed our problem =Win 10 start menu not dispalying menu (but had right click options), no right clicking on many apps including file explorer, etc.
I only need to be a SmbV1 client to connect to a Solaris 9 file server running a legacy version of Samba. It stopped working momentarily after a WIN10 upgrading around Oct. 2018 I think?- but googled and re-enabled SmbV1 feature and worked fine - and that was still enabled after running running WR .
Also in addition to not being able to access the Samba shared drive , I don't see all the other "workgroup" PC's (in the workgroup named "workgroup", which we started in the XP/98 days back in 2000 - and still have running virtual XP machines (in Oracle virtualbox) that can all see/use Samba shared drive. I never used/enabled a "Homegroup" in Windows 10 and am glad to see they stopped pushing it on us.
Also completely turned it off, then restart hoping it would want to update a relative driver, but no change.
Before I ran WR, I tried a restore point (from 12/17/19, and have only 1 earlier one that I could try now?) ran sfc /scannow, then malwarebytes and rkill & rebooted. No reported errors, rootkits, etc. - but I did not try "dism /restorehealth" . Then I ran WR v4.7.1 fixed which fixed our problem =Win 10 start menu not dispalying menu (but had right click options), no right clicking on many apps including file explorer, etc.
I only need to be a SmbV1 client to connect to a Solaris 9 file server running a legacy version of Samba. It stopped working momentarily after a WIN10 upgrading around Oct. 2018 I think?- but googled and re-enabled SmbV1 feature and worked fine - and that was still enabled after running running WR .
Also in addition to not being able to access the Samba shared drive , I don't see all the other "workgroup" PC's (in the workgroup named "workgroup", which we started in the XP/98 days back in 2000 - and still have running virtual XP machines (in Oracle virtualbox) that can all see/use Samba shared drive. I never used/enabled a "Homegroup" in Windows 10 and am glad to see they stopped pushing it on us.
Also completely turned it off, then restart hoping it would want to update a relative driver, but no change.