Show Seconds in the System Clock

 

Later versions of Windows 11 will have this in the taskbar settings.

Before that this registry key will activate the display of seconds on the taskbar clock.

To make Windows clock display seconds, open RegEdit to "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced" and create a new DWORD named "ShowSecondsInSystemClock" if it isn't present already. Set the value of "ShowSecondsInSystemClock" to 1.

Edge using different proxy settings to those on the system

 

If you see strange behaviour in Edge where certain websites do not load check the Edge proxy setting that may be applying in Intune.  It is possible that Edge is running different settings to the system proxy settings which could be very confusing.

Use this link to check what Edge is actually using for internet access settings

edge://application-guard-internals/#utilities

Proxy settings

\Microsoft Edge\Proxy server

Configures the proxy settings for Microsoft Edge. If you enable this policy, Microsoft Edge ignores all proxy-related options specified from the command line. If you don't configure this policy, users can choose their own proxy settings. This policy overrides the following individual policies: 'ProxyMode' (Configure proxy server settings) 'ProxyPacUrl' (Set the proxy .pac file URL) 'ProxyServer' (Configure address or URL of proxy server) 'ProxyBypassList' (Configure proxy bypass rules) Setting the 'ProxySettings' (Proxy settings) policy accepts the following fields: * ProxyMode, which lets you specify the proxy server used by Microsoft Edge and prevents users from changing proxy settings * ProxyPacUrl, a URL to a proxy .pac file * ProxyServer, a URL for the proxy server * ProxyBypassList, a list of proxy hosts that Microsoft Edge bypasses For ProxyMode, if you choose the value: * direct, a proxy is never used and all other fields are ignored. * system, the systems's proxy is used and all other fields are ignored. * auto_detect, all other fields are ignored. * fixed_servers, the ProxyServer and ProxyBypassList fields are used. * pac_script, the ProxyPacUrl and ProxyBypassList fields are used. For more detailed examples go to https://go.microsoft.com/fwlink/?linkid=2094936. Example value: { "ProxyMode": "pac_script", "ProxyPacUrl": "https://internal.site/example.pac", "ProxyServer": "123.123.123.123:8080", "ProxyBypassList": "https://www.example1.com,https://www.example2.com,https://internalsite/" } Compact example value: {"ProxyMode": "pac_script", "ProxyPacUrl": "https://internal.site/example.pac", "ProxyServer": "123.123.123.123:8080", "ProxyBypassList": "https://www.example1.com,https://www.example2.com,https://internalsite/"}

Setting type: Device

Supported on: Microsoft Windows 7 or later

• Enabled
• Disabled
• Not configured

Proxy settings

edge://edge-urls

 

edge://edge-urls

Critical place to see what Edge is actually using for proxy settings.  It might not be what you think!
edge://application-guard-internals/#utilities

Windows Power and Boot EventIDs

 

1. EventID 41: System Log It shows that your Windows computer rebooted without shutting down completely.

2. EventID 6005: System Log Source EventLog It indicates that the event log service was started.

3. EventID 1074: System Log Source User32 Your computer records this event when an application forces your laptop to shut down or restart. This event also helps you know when a user restarted or shut down the computer from the Start menu or by using CTRL+ALT+DEL.

from:

https://manage.accuwebhosting.com/knowledgebase/3897/How-to-check-shutdown-and-reboot-logs-in-Windows-servers.html#:~:text=Event%20ID%206005%3A%20It%20indicates,using%20CTRL%2BALT%2BDEL.

EventID 13: System Log The OS is shutting down

EventID 12: System Log The OS is starting

EventID 6006: System Log Source EventLog It indicates that the event log service is stopping. This is indicative of a shutdown/restart.

keywords
Event Log
Events

Failed to grab execution mutex. System error 258 / 1618

 

An MSI install exiting with a 1618 error and including a Failed to grab execution mutex. System error 258 might just need a restart on the target system.

Windows 10 / 11 Optional Features installation problem error 0x800f0954

OpenSSH Client and OpenSSH Client are Windows 10 optional features (OFs). Some OFs can’t be installed from powershell or the GUI (Apps & Features_Optional Features) because they are not included in the original image or accessible from WSUS or Windows Update.

Attempts to install via the GUI or powershell fail. The latter returning an error code 0x800f0954:






The GUI attempt helpfully responds:

Installation failed
Contact your administrator to get this feature

In order to install some optional features they must first be obtained from a separate media set known as Features On Demand (FOD). This is downloadable from Microsoft Volume Licensing Service Center (VLSC)

FODs do not appear to be Windows 10 version specific. Using the latest available seems to have backward compatibility. e.g. The 2004 FOD media has been used to apply the OpenSSH features to a Windows 10 20H2 verison. There is no 20H2 FOD media available on VLSC.

These can be mounted and the required CAB files copied out to the required location.

The recommended installation method is to copy the cabs to a folder on the target machine e.g. C:\temp\OpenSSHFODs then run the following elevated powershell command:

add-windowscapability -online -name OpenSSH.Client~~~~0.0.1.0 -source C:\temp\OpenSSHFODs -LimitAccess

Verify status of features

get-windowscapability -online | where name -like 'OpenSSH*'

Note that in this case with OpenSSH, related windows services may need to set from manual to automatic if required at system startup.

references:

Add-WindowsCapability (DISM)

Available features on demand

Use DISM in Windows PowerShell

Enable or Disable Windows Features Using DISM

Get started with OpenSSH for Windows

Scheduled Task Failure Error Code 0x80073a99

 

Scheduled Task Failure Error Code 0x80073a99

I set up two scheduled tasks with EventID triggers.  One with Basic and the other with Custom event specification.  The custom one failed to configure on the target as a scheduled task and the error code showed in the GPResult report for the target.

I used a custom event definition for the trigger because the the Event Source was not selectable in basic mode on the server where the GPO(GPP) was being defined.

The resolution was to define the GPO(GPP) on a computer where the Event Source could be selected in Basic Mode.  This computer needs to have the Admin Tools installed for the Group Policy Management tool to be available.