Mapping linux drive to windows 8.1 PC


 Share

Recommended Posts

Draconian Guppy

Warning, extreme linux noob here

NP.. SAMBA shares are awesome ;) sudo apt-get install samba :p

 

I am in the early process of converting my Win ServR2 box over for Sickbeard.. 

 

 

Use the Samba GUI, and you'll see how easy it is.

 

 

You ever used network shares in Windows (e.g. "\\MyPC\shared videos")? Samba is the Linux port of that, and the two are mostly compatible. I think in Ubuntu, Samba is integrated into Nautilus. You can just right click -> properties on a folder and share it.

 

EDIT: https://www.liberiangeek.net/2011/11/a-quick-way-to-share-folders-in-ubuntu-11-10-oneiric-ocelot/. This is for Oneiric, but presumably it still applies in Trusty.

 

 

You don't have to manually install it like that. Just use your distro's package manager. Either 'sudo apt-get install samba', 'yaourt -S samba', or something similar. If you're adverse to the cli, most distros come with a GUI that does the equivalent.

 

 

So fed up with windows drivers (ati) I decided to give ubuntu 14.04 a go. So I created all the necessary partitions (and managed to keep my existing ntfs info! ) that process was pretty straight forward booting from USB. I use this PC mostly as an internal fileserver over lan.

 

 

I tried right clicking creating a new share, tried via terminal, tried editing the conf. I got 3 different results, none accessible, see below:

 

YWd54Kt.jpg

 

 

 

Here's my smb.conf, which I basically did not modify, just to add another folder at the end.

 

 

 

 
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which 
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic 
# errors. 
 
#======================= Global Settings =======================
 
[global]
 
## Browsing/Identification ###
 
# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = WORKGROUP
 
# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)
 
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#   wins support = no
 
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z
 
# This will prevent nmbd to search for NetBIOS names through DNS.
   dns proxy = no
 
#### Networking ####
 
# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0
 
# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes
 
 
 
#### Debugging/Accounting ####
 
# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m
 
# Cap the size of the individual log files (in KiB).
   max log size = 1000
 
# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no
 
# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
   syslog = 0
 
# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d
 
 
####### Authentication #######
 
# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller". 
#
# Most people will want "standalone sever" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = standalone server
 
# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.  
   passdb backend = tdbsam
 
   obey pam restrictions = yes
 
# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes
 
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
 
# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
   pam password change = yes
 
# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user
 
########## Domains ###########
 
#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or 'domain logons' is set 
#
 
# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile
 
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U
 
# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd
 
# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u
 
# This allows machine accounts to be created on the domain controller via the 
# SAMR RPC pipe.  
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u
 
# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.  
; add group script = /usr/sbin/addgroup --force-badname %g
 
############ Misc ############
 
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /home/samba/etc/smb.conf.%m
 
# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap uid = 10000-20000
;   idmap gid = 10000-20000
;   template shell = /bin/bash
 
# Setup usershare options to enable non-root users to share folders
# with the net usershare command.
 
# Maximum number of usershare. 0 (default) means that usershare is disabled.
;   usershare max shares = 100
 
# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes
 
#======================= Share Definitions =======================
 
# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
;   comment = Home Directories
;   browseable = no
 
# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
;   read only = yes
 
# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
;   create mask = 0700
 
# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
;   directory mask = 0700
 
# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
;   valid users = %S
 
# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes
 
# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700
 
[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700
 
# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin
 
[Guppy]
path = /home/guppy/Desktop/guppy
available = yes
valid users = guppy
read only = no
browsable = yes
public = yes
writable = yes
 

 

Link to post
Share on other sites

Haggis

I have a guide i use in the house, i will find it when i get in and pop it to you

  • Like 1
Link to post
Share on other sites

Haggis

here is mine if it helps

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which 
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic 
# errors. 
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = MSHOME

# server string is the equivalent of the NT Description field
   server string = %h server

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#   wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
   dns proxy = no

# What naming service and in what order should we use to resolve host names
# to IP addresses
;   name resolve order = lmhosts host wins bcast

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
   syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
#   security = user

# You may wish to use password encryption.  See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
   encrypt passwords = true

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.  
   passdb backend = tdbsam

   obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
   pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
;   domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the 
# SAMR RPC pipe.  
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.  
; add group script = /usr/sbin/addgroup --force-badname %g

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
#   load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
;   printing = bsd
;   printcap name = /etc/printcap

# CUPS printing.  See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
;   printing = cups
;   printcap name = cups

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
#         SO_RCVBUF=8192 SO_SNDBUF=8192
#   socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
;   message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
#   domain master = auto

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap uid = 10000-20000
;   idmap gid = 10000-20000
;   template shell = /bin/bash

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
;   winbind enum groups = yes
;   winbind enum users = yes

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
;   usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes

#======================= Share Definitions =======================

[homes]
   comment = Home Directories
   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
   read only = no

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
   create mask = 0775

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
   directory mask = 0775

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# The following parameter makes sure that only "username" can connect
# to \\server\username
# This might need tweaking when using external authentication schemes
   valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin

# A sample share for sharing your CD-ROM with others.
;[cdrom]
;   comment = Samba server's CD-ROM
;   read only = yes
;   locking = no
;   path = /cdrom
;   guest ok = yes

[TV-Shows]
   comment = Some useful files
   read only = no
   locking = no
   path = /home/tv-shows
   guest ok = no

[Movies]
   comment = Some useful files
   read only = no
   locking = no
   path = /home/media
   guest ok = no
# The next two parameters show how to auto-mount a CD-ROM when the
#	cdrom share is accesed. For this to work /etc/fstab must contain
#	an entry like this:
#
#       /dev/scd0   /cdrom  iso9660 defaults,noauto,ro,user   0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
#	is mounted on /cdrom
#
;   preexec = /bin/mount /cdrom
;   postexec = /bin/umount /cdrom

  • Like 1
Link to post
Share on other sites

Draconian Guppy

thanks, Ill check as soon as  I get home.

Link to post
Share on other sites

Draconian Guppy

fixed using this:

 

If you?re unable to access the shares, go back to your Ubuntu machine and run the commands below:

sudo smbpasswd -a USERNAME

quick_share_oneiric_6_thumb.png

Replace USERNAME with your account name.

 

Now try again to access the shares from your Windows machine

 

To find your computer name in Ubuntu run the command below:

hostname

 

Enjoy!

 

 

Can't add tech points to myself eh?

Link to post
Share on other sites

Draconian Guppy

Cool thanks! 

  • Like 1
Link to post
Share on other sites

This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By anmol112
      How to fix Windows Hello not working in the latest Windows 11 build 22000.100
      by Anmol Mehrotra



      Yesterday, Microsoft released another Windows 11 build to Windows Insiders in the Dev Preview ring. The new build brought improvements to the UI as well as the new Microsoft Teams integration. However, it also came with a bunch of known issues, one of which was the broken Windows Hello.

      Fortunately, there is an easy fix for "Something went wrong" error when trying to use Windows Hello on Windows 11. If you are facing the issue, then you can follow the steps below to get the issue fixed:

      Click on Windows Search or the Windows button Type "Device Manager" and click on 'open'. You can also right-click on the Windows button and select Device Manager. Once Device Manager is opened, double-click on "Biometric devices" Now right-click on "Windows Hello Face Software Device" and click on 'uninstall device' Once done, reboot the system, let Windows download and install the latest drivers After the installation is finished, Windows Hello should be good to go. We hope Microsoft fixes this issue in the future build. While not critical, the issue certainly can be a pain for users who rely on Windows Hello to sign-in to their devices.

      For more information on Windows 11, you can check out our article on minimum system requirements as well as the list of CPUs that support Windows 11. Apart from the general requirements, Microsoft has also listed out specific feature requirements for Windows 11 including webcams, Bluetooth and Precision Touchpad on all upcoming laptops. Last month, Microsoft also updated the PC Health Check app to show why a device is not ineligible to receive the Windows 11 update. However, the company will allow some manufacturers to bypass the TPM 2.0 requirement and it is also allowing Windows Insiders with unsupported hardware to test Windows 11 Insider Builds. Several manufacturers have published a list of hardware that will be compatible with Windows 11.

      If you are still out of the loop, then you can check out hands-on video. If you want to get in-depth information about Windows 11 then you can check out our article covering all the new features and changes.

    • By Abhay V
      Here are the known issues in Windows 11 build 22000.100
      by Abhay Venkatesh

      Microsoft today rolled out Windows 11 build 22000.100 to Insiders running Dev channel builds. The cumulative update brings with it - among other things - improvements to the taskbar UI and the system tray, adding subtle design improvements, in line with the Windows 11 experience.

      The improvements include a better UI for the system tray, along with a new visual cue for when an app requires attention on the taskbar thanks to a background task. However, the ability to run Android apps, something that the firm announced during the Windows 11 unveil event, is yet to be added. When it does make it to the OS, it will happen through the Amazon Store that will be housed within the Microsoft Store.

      The firm isn't bringing any huge changes to the OS, as it is still addressing bugs and reliability concerns that are being reported by users running the Dev channel builds, while prepping the builds for the Beta channel. However, along with the list of bugs fixes, there are still a bunch of known issues that are being tracked. Here is the complete list of issues in Windows 11 build 22000.100:

      Issues such as the File Explorer bug might make it difficult for users to run apps reliably, so it is best to be aware of the problems before considering these builds for your daily driver. Additionally, there are some Windows Hello issues that have workarounds.

      Windows 11 build 22000.100 is rolling out via Windows Update to Dev channel users running the latest version of the OS. The release to the Beta channel should happen soon as the firm skipped releasing the latest 21H1 updates, citing the impending release of Windows 11 builds. Currently, there aren't any official ISOs available either for those hoping to perform a clean install of these builds.

    • By anmol112
      New Windows 11 concept shows what Task Manger with dark mode could look like
      by Anmol Mehrotra

      Source: Jakub Last month, Microsoft finally unveiled the much-anticipated Windows 11 update. The new update comes with an updated UI, performance, and productivity improvements. Microsoft has also released the minimum system requirements for Windows 11 which includes Secure Boot and TPM 2.0 among other things, but the latter can be bypassed for now.

      One of the key highlights of Windows 11 is the new rounded UI that is pleasing to the eye. Along with the new UI, Microsoft is also embracing the dark side with an improved system-wide dark mode. Unfortunately, the company has again skipped Task Manager for some reasons as the app still lacks support for dark mode.

      However, Twitter user Jakub has given us a look at what Task Manger could look like if Microsoft ever decides to add support for dark mode. The concept shows off Task Manager wrapped in dark background that blends in well with the wallpaper and compliments the text, which uses the new Segoe UI Variable Display font. The usage charts, on the other hand, may look familiar to anyone who has played around with Linux distros.

      Overall, the design looks elegant as well as gives users the ability to switch to dark mode on Task Manager. We do hope that Microsoft adopts the design or a variation of the design for Windows 11.

      For more information on Windows 11, you can check out our article on minimum system requirements as well as the list of CPUs that support Windows 11. Apart from the general requirements, Microsoft has also listed out specific feature requirements for Windows 11 including webcams, Bluetooth and Precision Touchpad on all upcoming laptops. Last month, Microsoft also updated the PC Health Check app to show why a device is not ineligible to receive the Windows 11 update. However, the company will allow some manufacturers to bypass the TPM 2.0 requirement and it is also allowing Windows Insiders with unsupported hardware to test Windows 11 Insider Builds. Several manufacturers have published a list of hardware that will be compatible with Windows 11.

      If you are still out of the loop, then you can check out hands-on video. If you want to get in-depth information about Windows 11 then you can check out our article covering all the new features and changes.

    • By Abhay V
      Microsoft says that there will be a Windows 11 LTSC release, but it's a few years out
      by Abhay Venkatesh

      Microsoft officially unveiled Windows 11 last month, showing off the UI changes being made as part of a major update to Windows, among other changes such as the addition of support for Android apps. The company also shared more about the support and service lifecycle of the OS, adding that Windows 11 will move to an annual update cadence, unlike Windows 10. It has also been providing clarifications about the minimum system specifications, which has been a topic of discussion since the Windows 11 announcement.

      As for Windows 10, the firm recently detailed the features being added to version 21H2, the next feature update to Windows 10 – which is yet another enablement package. As part of that announcement, the Redmond company also confirmed that the next Long-Term Servicing Channel (LTSC) version will be based on Windows 10 21H2 and will be released later this year. However, nothing in the way of information about Windows 11 LTSC releases was shared. That changed today, as the firm confirmed during an AMA on the Tech Community blog (spotted by Petri) that the LTSC release after the one based on 21H2 will be based on Windows 11.

      A response to one of the AMA questions explains:

      Microsoft recently revised the support timeframes for Windows LTSC releases from 10 years to five years, with the 2021 release being the first to be affected by the change. The current release based on version 1809, therefore, is unaffected and enjoys an extended support timeline till 2029. With the 2021 version likely supported only until 2026, there is less incentive for enterprises to move to a newer version, thanks in part to the reduced support.

      Today’s session also contained questions about the future of Windows 10 updates, with the company reiterating that it is “committed” to support Windows 10 till October 2025 for eligible customers – such as for non-LTSC SKUs. However, it adds that the question of whether version 21H2 will be the “last feature update” is still a topic of discussion internally.

      It will be interesting to see what the release timelines for the LTSC version based on Windows 11 will be. However, unlike Windows 10, the first Windows 11 version to be released later this year will not be accompanied by a corresponding LTSC release and is at least three years out.

    • By hellowalkman
      Microsoft provides workaround for HiveNightmare registry vulnerability that affects Windows 10 and 11
      by Sayan Sen



      Microsoft earlier today released a temporary workaround solution for systems that are vulnerable to the newly found HiveNightmare security flaw. The vulnerability was discovered by Twitter user 'Jonas L' and also verified by another user '@GossiTheDog' who noticed that the Windows Security Account Manager (SAM) database - that contains all important passwords and keys - was now apparently accessible by non-admin users. This is why the new flaw is called SeriousSAM or HiveNightmare as it gives an attacker access to SAM, SYSTEM, and SECURITY registry hive files.

      The problem was first introduced when Microsoft released the recent KB5004605 update that added Advanced Encryption Standard (AES) encryption and all OS versions starting from Windows 10 build 1809, including the latest Windows 11 Insider Preview Build 22000.71 are exploitable.

      Microsoft has acknowledged the vulnerability in the new CVE dubbed 'CVE-2021-36934' and has provided the following workaround:

      Restrict access to the contents of %windir%\system32\config Open Command Prompt or Windows PowerShell as administrator.

      Run this command:
      icacls %windir%\system32\config\*.* /inheritance:e

      Delete Volume Shadow Copy Service (VSS) shadow copies

      Open Command Prompt or Windows PowerShell as administrator.

      Run command: vssadmin list shadows to see if there are shadow points

      If there are, delete them with: vssadmin delete shadows /for=c: /Quiet

      Run command: vssadmin list shadows again to see if they are deleted

      Delete any System Restore points that existed prior to restricting access to %windir%\system32\config

      Create a new System Restore point (if needed)

      For those wondering if their system may be vulnerable to this exploit, most computers that have OS drives bigger than 128GB likely generate VSS shadow copies which can be exploited by an attacker. For those who wish to be sure if their system has created VSS files and whether their computer is exploitable, the CERT has provided an excellent guide to check how.

      Source: Microsoft via Forbes

      Update: As a reader 'Tantawi' has pointed out, we missed adding how a user would be able to delete their VSS shadows. The command that will do so can be found on Microsoft's official page here.