Remko Weijnen's Blog (Remko's Blog)

About Virtualization, VDI, SBC, Application Compatibility and anything else I feel like


7,898 views

If this is your first visit, take your time and look around. Here are some things you might be looking for:

Do you like my work? Did my work help you?

  • Leave a comment and tell me how it was usefull to you.
  • If you want you can make a donation with the Paypal Donate Button in the right Sidebar.

Thank you!

  • Comments Off on Dear Visitor
  • Filed under: Uncategorized
  • 171 views

    This content is password protected. To view it please enter your password below:

  • Enter your password to view comments.
  • Filed under: Uncategorized
  • 134 views

    After changing AWS accounts I resetup my API key so I could use the AWS PowerShell CmdLets.

    However even though I was sure I configured everything correctly I couldn’t call any EC2 cmdlet. More about that further below but let’s refresh how to setup an API key for PowerShell:

    The procedure to do this is quite simple:

    First you create an IAM user (go to Services | IAM) then in the left treeview select Users or use this direct link.

    Identity and Access Management (IAM) Treeview

    Click Add users or use this direct link, give the user a name and select “Access key – Programmatic access”

    In the next screen select the appropriate permissions, in this screenshot I’m using AdministratorAccess but this of course means you’re giving this user the permissions to do absolutely anything.

    So have a good look at the minimum permissions that you actually require.

    Click Next on the Add tags screen and the Review screen should look something like this:

    On the next screen you will get the Access key ID and the Secret access key. Note that this is the only time you will get to see the Secret access key so use the copy button or Download the .csv file (but delete it from disk when you’re done of course).

    Read the rest of this entry »

  • 0 Comments
  • Filed under: AWS, PowerShell
  • 150 views

    It’s been a while since I last wrote a post but it does feel good so I’m expecting to pick up blogging in a more regular cadence soon!

    This one is a quicky though, as I had an annoying issue with Ubuntu 22.04 VM’s running on VMware workstation.

    Every time I attempted to paste a (larger) file from the host it would crash Ubuntu’s File Explorer (Nautilus):

    Nautilus (Ubuntu's File Explorer) crashes when pasting a file from a VMware host

    click video above to play

    Fortunately I found a workaround:

    Read the rest of this entry »

  • 0 Comments
  • Filed under: Linux, Ubuntu, VMWare
  • 1,174 views

    I had a strange issue today: I couldn’t open any webpage in the Edge browser on my Windows 10 machine:

    Edge browser with error message "Can't reach this page"
    Edge browser: “Can’t reach this page”

    Network icon showing Internet access

    The network icon was showing that there was Internet access and a quick check on the command prompt showed that the connection (including name resolution appeared to work fine):

    Command prompt showing that ping to www.google.com works fine.ping www.google.comPinging www.google.com [172.217.168.196] with 32 bytes of data:
Reply from 172.217.168.196: bytes=32 time=15ms TTL=55
Reply from 172.217.168.196: bytes=32 time=14ms TTL=55Ping statistics for 172.217.168.196:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 15ms, Average = 14ms
    ping to www.google.com

    Other browsers such as Firefox (my default browser) and Chrome also worked fine but some other Microsoft applications also didn’t work such as the Microsoft Store:

    Read the rest of this entry »
  • 1 Comment
  • Filed under: Uncategorized
  • 413 views

    I had a strange error today using the Desktop App Converter with the parameters given from the Store for Business.

    The conversion would fail with the following error:

    DesktopAppConverter : error 'E_MANIFEST_USE_DEFAULT_VALUE_FAILED': Property 'Package.Applications.Application.Id' in AppxManifest.xml could not be set to the default value

    I’m not sure why this fails as the PackageName is provided by the store and should be valid. An answer on stackoverflow suggested to use a different value for the PackageName parameter and then edit the manifest.

    I don’t like this method as manual modifications of the manifest often leads to errors when submitting the application to the store.

    So let’s have a look and see why we’re getting this error.

    I searched for E_MANIFEST_USE_DEFAULT_VALUE_FAILED in the DesktopAppConverter folder and found 1 occurence in ManifestOps.ps1.

    From a look at the code it wasn’t immediately clear where the validation failed so I decided to debug it.

    Read the rest of this entry »

  • 1 Comment
  • Filed under: Uncategorized
  • 1,522 views

    I was trying to sign an .appx package that I created with the Desktop App Converter. However signtool returned the following error: Sign returned error: 0x800700C1
    For more information, please see http://aka.ms/badexeformat

    image

    Sadly signtool doesn’t return more detailed information, even when passing the debug switch:

    image

    So what’s going on?

    Read the rest of this entry »

  • 0 Comments
  • Filed under: UWP
  • 3,283 views

    Recently I installed a new Windows 10 machine (version 1709 aka Fall Creators Update).

    After a while I noticed a problem with the Task Scheduler: when I wanted to open the “Schedule Tasks” option from settings I received the following error message:

    The remote computer was not found.

    The Task Scheduler MMC snapin was empty:

    Task Scheduler (Local) | Empty

    Read the rest of this entry »

  • 0 Comments
  • Filed under: Windows 10
  • 251 views

    DAC IconWhen using the Desktop App Converter there’s no need to sign the resulting .appx packages with your own code signing certificate when you submit them to the Store.

    However if you want to test the package on a different machine or distribute it to test users you may want to sign the .appx with a certificate.

    One option is to use the -sign parameter, in this case the Desktop App Converter generates a code signing certificate and signs the package with it. Although easy to use, it’s not very convenient if you want to distribute the .appx as you need to add the certificate to the Trusted People certificates store (for each user). See Run the Packaged App in the documentation.

    imageIf you want to sign the .appx package with a trusted certificate (e.g. issued by a trusted certificate authority such as DigiCert) you need to make sure that you pass the subject (the CN) from your code signing certificate to the Desktop App Converter (using the -Publisher parameter).

    Read the rest of this entry »

  • 0 Comments
  • Filed under: UWP
  • 1,066 views

    Just a very quick note here (mostly a note to self) but I had a couple of folder from previous Windows 10 installations named Windows.old Windows.old(1), Windows.old(2) etc.

    These folders should be removed when you use Disk Cleanup and select the “Remove previous Windows Installation(s)” option.

    DiskCleanup

    However I already did that and for some reasons a subfolder named C:\Windows.old\Users\<username>\AppData\Local\Packages\Microsoft.Windows.Cortana_cw
    5n1h2txyewy\LocalState
    couldn’t be deleted and therefore the parent folder couldn’t be deleted.

    I couldn’t delete them with Windows Explorer nor via the cmd prompt or PowerShell. Then I tried to use the \\? prefix and that worked:

    image

  • 0 Comments
  • Filed under: Windows 10
  • 629 views

    I have been working with Microsoft’s Desktop App Converter a lot recently. Even though there’s an option to autosign the resulting package with the -Sign switch I prefer to sign APPX packages myself using signtool.

    The reason is that I can send UWP packages to testers for sideloading without requiring them to import the auto generated certificate (which is different on each (re)build).

    However I always forget the exact path to signtool.exe (this comes with the Windows SDK).

    The Windows 10 SDK is installed by default in C:\Program Files (x86)\Windows Kits\10.

    Signtool.exe will be in the folder<sdkpath>\bin\<version>\<platform>\signtool.exe.

    As there are multiple version of Windows 10 there are multiple version of the SDK and you can install those concurrently.

    But then I found the PowerShell cmdlet Resolve-Path which “Resolves the wildcard characters in a path, and displays the path contents”.

    This does exactly what I need:

    image

    Wow, Resolve-Path is a perfect example of the many hidden gems in PowerShell!

    So I decided to wrap signtool.exe in a PowerShell cmdlet as PowerShell also makes it easy to locate the correct code signing certificate from the certificate store. Read the rest of this entry »

  • 0 Comments
  • Filed under: PowerShell
  • Blogroll


    Categories


    Archives