This post describes how you can filter the results from the Get-WinEvent PowerShell command so only certain entry types are shown e.g. error entries only. Resolution Use -FilterHashTable and Level='2'.  You can also specify other levels to show different entry types. Get-WinEvent -MaxEvents 1 -FilterHashTable @{LogName='System';Level='2'} | Format-Table -Wrap

This post describes how to get the full event log message using the Get-EventLog PowerShell command which, by default, will truncate the message: Resolution Use Format-Table -Wrap: Get-EventLog Application -Newest 1 | Format-Table -Wrap Use -ExpandProperty: Get-EventLog Application -Newest 1 | Select -ExpandProperty Message

This post describes why the exFAT option is sometimes missing from the File system drop down when formatting a hard disk drive volume in Windows using Disk Management. Cause This issue can occur when the size of the volume you are formatting is less than 32GB, which is the maximum partition size limit using the FAT or FAT32 file system format on Windows. If you format a volume below 4GB, you will see FAT and FAT32 in the file system drop down, but not exFAT, as per the screenshot above. If you format a volume above 4GB but below 32GB, you will see FAT32 in the file system drop down, but not exFAT: Resolution If you format a volume above 32GB, you will see exFAT in the file system drop down: Alternatively, you can use format.exe in a command prompt to format the volume as exFAT.

This post describes an alternative way to get a volume's file system type when it is formatted as exFAT and PowerShell Get-Volume returns the data as Unknown. Here is an exFAT volume in Disk Management: PowerShell Get-Volume returns FileSystemType Unknown  If I run the PowerShell command Get-Volume on Windows Server 2019 or Windows 10, the FileSystemType for the exFAT volume is returned as Unknown: Resolution To resolve the issue, you can get the data using the Win32_Volume class: Get-CimInstance Win32_Volume|SELECT DriveLetter, Label, FileSystem

This post describes how to add a Camtasia cursor effect to simulate and indicate a mouse click by making the mouse size change, similar to the effect seen in the Camtasia Tutorials. The effect can easily be created by using a simple animation. 1. Change the default cursor size to 150% across the entire clip 2. Add a Custom animation where you want to indicate a mouse click.  Shorten the animation length to about 0.1 seconds. 3. Set the cursor size to 100% after the animation 4. Add a second Custom animation and place this directly after the first animation 5. Set the cursor size back to 150% after the second animation 6. Fine tune the position of the animations if required.  The middle of the animation should be lined up with where you want to simulate a mouse click. Double click To simulate a double click, simply copy and paste the two animations above and put them all next to each other. Quickly apply elsewhere Once created, you can easily use the cursor effect in other part...

This post describes how to fix a problem in which Camtasia Behaviors, Cursor Effects, Audio Effects and Visual Affects are empty with no effects showing: This happened after I first installed Camtasia 2020. Resolution The resolution turned out to be quite easy.  I simply closed Camtasia then re-opened it.  The Behaviors, Cursor Effects, Audio Effects and Visual Affects now appeared as expected: Related Posts -  Camtasia cursor effect to simulate and indicate a mouse click -  Open camproj file in Camtasia 2020

This post describes how to fix the error: A file that is required cannot be installed because the cabinet file has an invalid digital signature. This may indicate that the cabinet file is corrupt. Cause This can occur when certificates from the cabinet file's digital signature certificate trust chain are missing and cannot be validated.  This can happen when you're running an installer in an environment that's not connected to the Internet and is therefore unable to update the trusted certificate authorities automatically. Resolution Right click the cabinet file, go to the Digital Signatures tab, press Details, then View Certificate and check the Certification Path.  This shows the certificates required to complete the trust chain. Next, download and install any certificates that are missing from the trust chain. Related Posts .NET Framework has not been installed because a certificate chain could not be built to a trusted root authority An update is available that enables ...

This page describes how to fix the error: Connection Failed. The request failed with HTTP status 401: Unauthorized. Cause This can occur when you try to establish a HTTP connection to an IIS server but the Windows Authentication Role Service has not bee installed. It can also occur if the IIS server requires a client certificate and this hasn't been provided by the client. Resolution Add the Windows Authentication Role Service to IIS: After Windows Authentication has installed, ensure the required Providers have been added e.g. Negotiate and NTLM.

 This post describes how to open a .camproj file in Camtasia 2020. I was previously using Camtasia Studio 8, which saves projects as a .camproj file type. Camtasia 2020 saves projects as a .tscproj file type and cannot open .camproj files. Resolution Camtasia 2019 can open .camproj files and convert them to the new .tscproj format, which can then be opened in Camtasia 2020. Download Camtasia 2019 Camtasia 2019 can be downloaded here: https://www.techsmith.com/download/oldversions Open in Camtasia 2020 When you open the converted .tscproj file in Camtasia 2020, you get prompted to convert it again: You may need to fix some annotations:  For example, one of my annotations looked very squashed after the conversion: Related Posts -  Camtasia Behaviors, Cursor, Audio and Visual Effects empty with no effects showing -  Camtasia cursor effect to simulate and indicate a mouse click

This post describes how to fix the error: The WS-Management service cannot process the request. The service is configured to not accept any remote shell requests. For more information, see the about_Remote_Troubleshooting Help topic. Cause This error can occur when the policy setting 'Allow Remote Shell Access' is disabled: If this policy is set to 'disabled', new remote shell connections are rejected by the server. The recommendation from Microsoft is to only disable this policy setting if you don't need PowerShell Remoting. Resolution To resolve the issue, change the 'Allow Remote Shell Access' policy setting to 'Enabled'. Video Link: The WS-Management service cannot process the request. The service is configured to not accept any remote shell requests. Related Posts -  The WinRM client cannot process the request. The authentication mechanism requested by the client is not supported...