Archive for the ‘Windows’ Category
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/07/16
It seems netsh is something different than bash or csh as it is the command-line interface to many (all?) Windows Firewall settings.
So I need to put some time into learning it.
This gives you all the names of firewall rules, ready for text searching it (with find, grep, etc):
netsh advfirewall firewall show rule name=all
An alternative might be PowerShell as it too has a lot of Windows Firewall plumbing: [WayBack] How to manage the Windows firewall settings with PowerShell – James O’Neill’s blog
Choices, choices.
–jeroen
via: [WayBack] windows firewall – How can I use netsh to find a rule using a pattern – Server Fault
Posted in Firewall, Power User, Windows | Leave a Comment »
Posted by jpluimers on 2018/06/29
I forgot to schedule the post below. It is still relevant if you create a machine with lots of Delphi versions on it.
Read the rest of this entry »
Posted in .NET, .NET 2.0, .NET 3.0, .NET 3.5, Database Development, Delphi, Delphi 2007, Delphi XE, Delphi XE2, Delphi XE3, Delphi XE4, Delphi XE5, Development, Firebird, InterBase, Power User, Software Development, Windows, Windows 8 | 2 Comments »
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/06/29
Some historic perspective (although on Windows since quite a long time, you can rename files before replacing them: that works very well):
[WayBack] Wer kann mir erklären: Warum braucht ein Windows10-Update heute immer noch mehrere Reboots? – Kristian Köhntopp – Google+
Zu MS-DOS Zeiten gab es kein Netz und kein Multiprocessing. Als Netz und Fileshares dann dazu kamen, funktionierten viele Anwendungen nicht korrekt.
Zu dieser Zeit hat Microsoft die Entscheidung getroffen, vom Betriebssystem aus Mandatory File Locking für geöffnete Dateien zu implementieren, es sei denn, ein Prozeß stellt das von sich aus anders ein.
Mandatory File Locking heißt in diesem Fall, daß nix und niemand eine Datei anfassen kann, die offen ist, Ein laufendes Executeable, eine DLL oder ein Logfile sind aber immer offen.
Daher gibt es einen Reboot Hook, mit dem ein Updater Dateiersetzungen für einen System Neustart hinterlegen kann. Beim Reboot werden die Dateien dann schnell ausgetauscht bevor sie geöffnet werden.
–jeroen
Posted in History, Power User, Windows | Leave a Comment »
Posted by jpluimers on 2018/06/29
When generating the Spring4D documentation at https://spring4d.4delphi.com/ using Documentation Insight by DevJet, I got this error:
HHC6003: Error: The file Itircl.dll has not been registered correctly.
Microsoft HTML Help Compiler 4.74.8702
Solving it turned out easy:
regsvr32 "%ProgramFiles(x86)%\Documentation Insight 3\Compilers\CHM\itcc.dll"
I got there via [WayBack] HTML Help FAQ – Wiki.HelpMVP.com:
“HHC6003: The file itircl.dll has not been registered correctly”
This error effects only a small number of users. A HH component (c:\windows\system\itcc.dll) did not get installed or registered correctly. If not installed get the DLL from another PC containing Workshop. To register the DLL run
regsvr32 c:\windows\system\itcc.dll (this path may be different for your PC – eg. c:\winnnt\system32).
This fix was originally reported by MVP David Liske: [WayBack] http://www.mvps.org/htmlhelpcenter/itircl.htm
–jeroen
Posted in Power User, Windows | Leave a Comment »
Posted by jpluimers on 2018/06/25
Posted in Microsoft Surface on Windows 7, Power User, Windows, Windows 10, Windows 7, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Vista, Windows XP | Leave a Comment »
Posted by jpluimers on 2018/06/19
Thanks [WayBack] gbabu for the below PowerShell ide
As PowerShell command:
Get-EventLog System | Where-Object {$_.EventID -eq "1074" -or $_.EventID -eq "6008" -or $_.EventID -eq "1076"} | ft Machinename, TimeWritten, UserName, EventID, Message -AutoSize -Wrap
Based on it and my own experience, thse Event IDs can be interesting:
- 41 – The system has rebooted without cleanly shutting down first
- 109 – The kernel power manager has initiated a shutdown transition.
- 1073 – The attempt by user [domain]\[username] to restart/shutdown computer [computername] failed.
- 1074 – The process [filename].[extension] has initiated the restart of computer [computername] on behalf of user [domain]\[username\ for the
- 1076 – ???
- 6008 – The previous system shutdown at [time-in-local-format] on [date-in-local-format] was unexpected.
You can also run this as a batch file, but not you need to escape the pipe | into ^| like this:
PowerShell Get-EventLog System ^| Where-Object {$_.EventID -eq "1074" -or $_.EventID -eq "6008" -or $_.EventID -eq "1076"} ^| ft Machinename, TimeWritten, UserName, EventID, Message -AutoSize -Wrap
If you have PowerShell 3.0 or greater, then you can use the [Archive.is] -In operator:
PowerShell Get-EventLog System ^| Where-Object {$_.EventID -in "41", "109", "1074", "6008", "1076"} ^| ft Machinename, TimeWritten, UserName, EventID, Message -AutoSize -Wrap
–jeroen
Posted in Batch-Files, CommandLine, Development, Power User, PowerShell, PowerShell, Scripting, Software Development, Windows | Leave a Comment »
Posted by jpluimers on 2018/06/04
RDP Wrapper works as a layer between Service Control Manager and Terminal Services, so the original termsrv.dll file remains untouched. Also this method is very strong against Windows Update.
I’ve tested this on Windows 7 Home Premium and it works fine, see the log below. On Windows 10 Fall Creators Update and up, I had to get the rfxvmt.dll files (in %windir%\System32 and %windir%\SysWOW64) from a Windows Professional system, see Known Issues. You can download them from the repository as well.
- Download from github.com/stascorp/rdpwrap/releases
- Unzip
- Run the
install.bat:
C:\Users\jeroenp\Downloads\RDPWrap-v1.6.1>install.bat
RDP Wrapper Library v1.6
Installer v2.3
Copyright (C) Stas'M Corp. 2016
[*] Notice to user:
- By using all or any portion of this software, you are agreeing
to be bound by all the terms and conditions of the license agreement.
- To read the license agreement, run the installer with -l parameter.
- If you do not agree to any terms of the license agreement,
do not use the software.
[*] Installing...
[*] Terminal Services version: 6.1.7600.16385
[+] This version of Terminal Services is fully supported.
[+] TermService found (pid 1168).
[*] Shared services found: CryptSvc, Dnscache, LanmanWorkstation, NlaSvc
[*] Extracting files...
[+] Folder created: C:\Program Files\RDP Wrapper\
[*] Downloading latest INI file...
[+] Latest INI file -> C:\Program Files\RDP Wrapper\rdpwrap.ini
[+] Extracted rdpw64 -> C:\Program Files\RDP Wrapper\rdpwrap.dll
[+] Extracted rdpclip6164 -> C:\Windows\System32\rdpclip.exe
[*] Configuring service library...
[*] Checking dependencies...
[*] Checking CertPropSvc...
[*] Checking SessionEnv...
[*] Terminating service...
[*] Starting CryptSvc...
[*] Starting Dnscache...
[*] Starting LanmanWorkstation...
[*] Starting NlaSvc...
[-] StartService error (code 1056).
[*] Starting TermService...
[*] Configuring registry...
[*] Configuring firewall...
OK.
[+] Successfully installed.
______________________________________________________________
You can check RDP functionality with RDPCheck program.
Also you can configure advanced settings with RDPConf program.
Druk op een toets om door te gaan. . .
C:\Users\jeroenp\Downloads\RDPWrap-v1.6.1>rdpcheck
Note that this “error” is normal: [-] StartService error (code 1056). as it means the service is already started: [WayBack] System Error Codes (1000-1299) (Windows)
ERROR_SERVICE_ALREADY_RUNNING
- 1056 (0x420)
- An instance of the service is already running.
–jeroen
Posted in Power User, Remote Desktop Protocol/MSTSC/Terminal Services, Windows | Leave a Comment »
Posted by jpluimers on 2018/05/28
As of Windows 10 fall creators update, the WDAGUtilityAccount was added, so the default accounts on such a machine are these:
- Administrator
- DefaultAccount
- Guest
- WDAGUtilityAccount
Then there is one account for the user that installed the system (which is named by that user).
Windows Defender Application Guard is the reason for WDAGUtilityAccount as explained here:
–jeroen
Posted in Power User, Windows, Windows 10 | Leave a Comment »