If you find that login occurs, but no desktop just blackscreen, add the local users “Interactive” and “Authenticated Users” to the local group “Users”, i.e.:
net localgroup Users Interactive /add net localgroup Users "Authenticated Users" /add
If you find that login occurs, but no desktop just blackscreen, add the local users “Interactive” and “Authenticated Users” to the local group “Users”, i.e.:
net localgroup Users Interactive /add net localgroup Users "Authenticated Users" /add
If your software is all new, let’s say 2013 and after, it probably makes sense to disable 8.3 filename generation, for a nice kick of speed.
To do it once for all drives, just do this:
fsutil behavior set Disable8dot3 1
If you want to do it for one select drive, say E:, first do a registry edit in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
you’ll want to change NtfsDisable8dot3NameCreation
to 2. Then you will need to reboot, and in an administrative command prompt:
fsutil behavior set E: 1
and reboot again, and it’s done.
Some articles:
https://msdn.microsoft.com/en-us/library/windows/desktop/ff384840(v=vs.85).aspx).aspx
https://blogs.technet.microsoft.com/filecab/2014/06/25/the-end-is-nigh-for-frs/
First, set the primary DNS as a static primary, bypassing DHCP for DNS only:
netsh interface ip set dns name="Local Area Connection" static 8.8.8.8 primary
Then, add the secondary DNS:
netsh interface ip add dns name="Local Area Connection" 8.8.4.4 index=2
In the example above, 8.8.8.8 is being set as primary, and 8.8.4.4 as secondary; these are Google’s public DNS servers, quite useful in some circumstances. On many systems the names of the interfaces (above, “Local Area Connection”) will have to be changed, either to “Local Area Connection 2” or something more different for wireless; you can get the names using ‘ipconfig’ (they are prefixed with “Ethernet adapter”, take those two words off and you have it) or GUI.
Microsoft is pushing all of its favorite customers very hard to upgrade to Windows 10, to the point that many are hurting themselves accidentally. Here we have a tool which eliminates the problem:
Here’s some good info:
If you see these in event logs, you are seeing the result of a mismatch between the running drivers in your machine and something in Microsoft’s cloud-based driver database. Do this:
This is an error common on SBS 2011. A simple fix which sometimes works, on the bottom of this page:
http://blog.mpecsinc.ca/2010/12/sbs-2011-error-wbcommandletinbuilttraci.html
The summary:
DEL C:\Windows\Logs\WindowsServerBackup\WBC*
Some Windows Update issues are permissions problems, which can be fixed using a method involving SUBINACL:
https://support.microsoft.com/en-us/kb/968003#/en-us/kb/968003
First, from administrative CMD:
wusa /uninstall /kB:3035583 wusa /uninstall /kB:2952664 wusa /uninstall /kB:2976978 wusa /uninstall /kB:3021917 wusa /uninstall /kB:3044374 wusa /uninstall /kB:2990214
Then you need to prevent the same updates from being reinstalled, from the Windows Installer GUI in the Control Panel.