Archive for the ‘Windows 8.1’ Category
Posted by jpluimers on 2019/03/22
Just out of curiosity, I wanted to try run a CHKDSK at boot time of a non-system disk.
The trick appears to be to ensure something locks the drive. An easy way to do that is have a command prompt open inside a directory on that drive.
The below example show just that: a regular command prompt locking the E: drive and an administrative command prompt scheduling the check at boot time:
In text
Regular command prompt:
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Users\jeroenp>e:
E:\>cd $RECYCLE.BIN
E:\$RECYCLE.BIN>
Administrative command prompt:
C:\WINDOWS\system32>chkdsk /R /F E:
The type of the file system is NTFS.
Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) n
Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) y
This volume will be checked the next time the system restarts.
C:\WINDOWS\system32>
–jeroen
Posted in Power User, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1 | Leave a Comment »
Posted by jpluimers on 2019/01/09
In my search for starting the Windows Credential Manager from the console, I found [WayBack] Credential Manager Shortcut – Create – Windows 7 Help Forums explaining:
%windir%\explorer.exe shell:::{1206F5F1-0569-412C-8FEC-3204630DFB70}
This reminded me of From batch file or shortcut: start Windows Update (via: Windows 7 Help Forums) and batch-file trick: Starting Windows Explorer and selecting a file (“explorer” commandline parameters “/n” “/e” “/select” “/root” “/start” site:microsoft.com).
The odd thing is that some of the GUID shortcuts works fine using the shell::: syntax, but fail with the /e:: syntax, for instance Windows Update until Windows 8.1:
%windir%\explorer.exe shell:::{36eef7db-88ad-4e81-ad49-0e313f0c35f8}
%windir%\explorer.exe /e,::{36eef7db-88ad-4e81-ad49-0e313f0c35f8}
One day I’ll create a table of permutations for various Windows versions and execute options.
For now these links need to suffice:
–jeroen
Posted in Batch-Files, Development, Power User, Scripting, Software Development, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows 9 | 1 Comment »
Posted by jpluimers on 2018/12/07
If adding a Windows machine to a Samba domain fails and the below “solves” your issue, then you need to tighten the security on the Samba side:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters]
; Enable NT-Domain compatibility mode
; Default:
; [value not present]
; "DomainCompatibilityMode"=-
"DomainCompatibilityMode"=dword:00000001
; Disable required DNS name resolution
; Default:
; [value not present]
; "DNSNameResolutionRequired"=-
"DNSNameResolutionRequired"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Netlogon\Parameters]
; Disable requirement of signed communication
; My Samba (3.0.33) works with signed communication enabled, so no need to disable it.
; Default:
; "RequireSignOrSeal"=dword:00000001
; Disable the usage of strong keys
; Default:
; "RequireStrongKey"=dword:00000001
"RequireStrongKey"=dword:00000000
–jeroen
Posted in *nix, *nix-tools, Power User, samba SMB/CIFS/NMB, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows 9 | Leave a Comment »
Posted by jpluimers on 2018/11/14
Dumping the command prompt history
From [WayBack] Saving windows command prompt history to a file – Charlie Arehart’s ColdFusion Troubleshooting Blog:
doskey /history
gives you the command history.
Redirecting with >, >> or piping with | allows you to save this to a file or filter the output.
Found via: [WayBack] How I can export the history of my commands in Windows(7) Command Prompt? – Stack Overflow
Shells that do support persistent history
Note that the command history is not persistent. If you want that, then there are two other shells that support persistent history:
Both of these found through [WayBack] windows – Is there a global, persistent CMD history? – Server Fault.
–jeroen
Posted in Microsoft Surface on Windows 7, MS-DOS, Power User, Windows, Windows 7, Windows 8, Windows 8.1 | Leave a Comment »
Posted by jpluimers on 2018/09/17
Steps to try first:
- Check
%windir%\Windowsupdate.log (on my system, it did not reveal anything special)
- In an administrator command prompt, run
sfc /scannow (which takes a few minutes to run)
- Reboot
- Run Clean Manager
%windir%\System32\cleanmgr.exe (ensure to clean up update files: it can take tens of minutes to run)
- Reboot
- Download the SP1 files (I needed 32-bit x86)
- Install SP1 manually
- If it still hangs:
- In
Appwiz.cpl try a “Repair” of the Office 2013 installation
- If it works: Reboot, otherwise:
- Uninstall Office 2013
- Disable the network adapter
- Reboot
- Check if KB3173424 is installed (check it with
Appwiz.cpl)
- if not: download on a different machine, transfer over USB, install, then reboot
- Check ifKB3172614 is installed (which has a younger Windows Update Client)
- if not: downloadon a different machine, transfer over USB, install, then reboot
- Enable the network adapter
- Let Windows scan for updates and install them
- If you get an error 80070463 or 80070663: just reboot and retry the updates.
- Reboot
- Run Clean Manager
- Install Office 2013
- Reboot
- Let Windows scan for updates and install them
- Reboot
- Run Clean Manager
- Reboot
The KB3172614 should also alleviate long during (dozens of minutes) high CPU usage of svchost.exe and TiWorker.exe when searching for Windows updates.
Read the rest of this entry »
Posted in Office, Office 2013, Power User, Windows, Windows 8.1 | Leave a Comment »
Posted by jpluimers on 2018/07/27
This worked for Windows 8.1 as well: Trying fix for Windows 8 high CPU usage of TiWorker.exe (via: bit-tech.net) « The Wiert Corner – irregular stream of stuff
DISM /online /cleanup-image /restorehealth
After more than one hour of running, it:
- freed up more than a gigabyte of disk space. Which on an SSD based VM is a lot.
- solved the huge memory footprint of TiWorker.exe on the right.
–jeroen
Posted in Power User, Windows, Windows 8, Windows 8.1 | Leave a Comment »
Posted by jpluimers on 2018/06/29
If you get the below error, then your RDP target server needs to be patched.
You can choose to stay vulnerable and modify your policy or registry settings as explained in the first linked article below: that is a temporary “workaround” which I do not recommend. Please update your RDP target servers in stead.
English:
[Window Title]
Remote Desktop Connection
[Content]
An authentication error has occurred.
The function requested is not supported
Remote computer: rdp.example.org
This could be due to CredSSP-encryption Oracle remediation.
For more information, see https://go.microsoft.com/fwlink/?linkid=866660
[OK]
Read the rest of this entry »
Posted in Power User, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows 9, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016 | Leave a Comment »
Posted by jpluimers on 2018/03/21
About a year ago, [WayBack] Rumors of Cmd’s death have been greatly exaggerated – Windows Command Line Tools For Developers got published as a response to confusing posts like these:
But I still think it’s a wise idea to switch away from the Cmd and to PowerShell as with PowerShell you get way more consistent language features, far better documentation, truckloads of new features (of which I like the object pipeline and .NET interoperability most) and far fewer quirks.
It’s time as well, as by now, Windows 7 has been EOL for a while, and Windows 8.x is in extended support: [WayBack] Windows lifecycle fact sheet – Windows Help:
| Client operating systems |
Latest update or service pack |
End of mainstream support |
End of extended support |
| Windows XP |
Service Pack 3 |
April 14, 2009 |
April 8, 2014 |
| Windows Vista |
Service Pack 2 |
April 10, 2012 |
April 11, 2017 |
| Windows 7* |
Service Pack 1 |
January 13, 2015 |
January 14, 2020 |
| Windows 8 |
Windows 8.1 |
January 9, 2018 |
January 10, 2023 |
| Windows 10, released in July 2015** |
N/A |
October 13, 2020 |
October 14, 2025 |
Which means the PowerShell version baseline on supported Windows versions is at least 4.0: [Archive.is] windows 10 powershell version – Google Search and [WayBack] PowerShell versions and their Windows version – 4sysops
PowerShell and Windows versions ^
| PowerShell Version |
Release Date |
Default Windows Versions |
| PowerShell 2.0 |
October 2009 |
Windows 7 Windows Server 2008 R2 (**) |
| PowerShell 3.0 |
September 2012 |
Windows 8 Windows Server 2012 |
| PowerShell 4.0 |
October 2013 |
Windows 8.1 Windows Server 2012 R2 |
| PowerShell 5.0 |
April 2014 (***) |
Windows 10 |
So try PowerShell now. You won’t regret it.
–jeroen
via: [WayBack] Very interesting clear-up post and comments on CMD, command.com, PowerShell in past and future DOS/Windows versions and Unix shells altogether. – Ilya S – Google+
Posted in Batch-Files, CommandLine, Development, Power User, PowerShell, Scripting, Software Development, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016 | Leave a Comment »
Posted by jpluimers on 2018/03/09
Windows 10 (and 8) include a new virtual memory file named swapfile.sys. It’s stored in your system drive, along with the pagefile.sys and hiberfil.sys. But why does Windows need both a swap file and a page file?
…
In summary, the swapfile — swapfile.sys — is currently used for swapping out Microsoft’s new style of app. Microsoft has called these universal apps, Windows Store apps, Metro apps, Modern apps, Windows 8 apps, Windows 8-style UI apps, and other things at various points.
via:
Posted in Power User, Windows, Windows 10, Windows 8, Windows 8.1, Windows 9 | Leave a Comment »
Posted by jpluimers on 2018/02/26
Posted in Power User, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016 | Leave a Comment »
The Wiert Corner - irregular stream of stuff 