Archive for the ‘Windows 8’ Category
Posted by jpluimers on 2019/10/25
By default, Chrome uses the same proxy server as Internet Explorer: the system one that your Chrome settings page accesses from chrome://settings/search#proxy through this command-line call:
"C:\Windows\system32\rundll32.exe" C:\Windows\system32\shell32.dll,Control_RunDLL C:\Windows\system32\inetcpl.cpl,,4
There is no GUI way inside Chrome to change this, but there is a command-line parameter: --proxy-server="ipaddress:port"
So create a new shortcut to Chrome, then you can change it.
This comes in very handy if you want to test
- some sessions through for instance Internet Explorer going through HTTP Fiddler (that defaults at localhost:8888)
- other sessions through Cntlm (that defaults to localhost:3128)
Some background information:
–jeroen
Posted in Chrome, Cntlm, NTLM, Power User, Web Browsers, Windows, Windows 7, Windows 8, Windows 8.1, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Vista, Windows XP, Windows-Http-Proxy | Leave a Comment »
Posted by jpluimers on 2019/05/20
- go to control panel | display
- change the screen resolution. the artifact will go away
- click on cancel when windows asks you if you want to keep the new resolution.
this works on laptops too.
[WayBack] User mahesh – Super User answering [WayBack] How to clear screen artifacts without rebooting Windows (multiple versions) – Super User
–jeroen
Posted in Power User, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Vista, Windows XP | Leave a Comment »
Posted by jpluimers on 2019/05/14
Posted in Batch-Files, Development, Microsoft Surface on Windows 7, Power User, Scripting, Software Development, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows 9, Windows Server 2000, 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 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/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
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 »
The Wiert Corner - irregular stream of stuff 