You Will Need Windows 10 Version 1803 Or Later To Install This App

2 views

Skip to first unread message

Ilario Grijalva

unread,

Aug 3, 2024, 4:59:55 PM8/3/24

to vietravadal

Do I need all those updates if I am installing 1803 fresh through our whole organization? I selected 1809 in my products because I myself am running 1809 so that I can see about the stability before upgrading anyone else if we decide to do that.

Also take a look at WSUS Automated Maintenance (WAM) to automate the processes of maintenance for you. Check out the Features ( Features of WAM WSUS Automated Maintenance AJ Tek ), Removal Records ( -records/ ), and see what others are saying about us on our Testimonials page ( Testimonials - AJ Tek Corporation ).

Right, so my WSUS is 2012 R2 as well and I have those same options and I checked the options for the servicing drivers. Now that I look at this, I guess I was assuming the cumulative updates for 1803/9 were coming from those extra selections I made, but in reality they were coming from the base Windows 10 option we both have selected.

This is a brand new clean install of Windows 10 1803 that I did for testing on a VM. One thing to note is that I did set TargetReleaseVersionInfo to 1803 to ensure that it didn't upgrade before I switched to Intune. That was just removed Monday so at this point its only been a few days.

As for the Report it shows Offering, but a few things stand out but both of these could be related to running an outdated version of Windows 10 since you need 1903 or later for the Compliance Reports.

At one time I installed OpenSSH Client as an Optional Feature when running Fall Creators Update (version 1709). I've since updated Windows to version 1803 and I no longer have OpenSSH Client installed. How do I get it back?

My understanding is that after updating to Windows 10 version 1803 (April 2018), OpenSSH client is automatically installed. However, it's not installed and the information I've seen online for how to install OpenSSH appears to be for previous versions of Windows 10, when OpenSSH Client was in beta.

When I had the Fall Creators Update (version 1709) and OpenSSH was in beta, I successfully installed it using the above Manage Optional Features. I don't know why it's not installed now and I can't find it anywhere to install.

When looking at See optional feature history, I see that OpenSSH Client was installed on 4/12/18 and uninstalled on 8/10/18. I don't recall explicitly uninstalling it, but that's the same day I installed a number of Windows updates and had to reboot a couple of times after updating.

I've also tried looking for it under the standard Windows Features (Turn Windows Features on and off) as suggested by this answer and I do not see it listed. (I've even tried expanding all of the collapsible items just to make sure it wasn't hiding under IIS or something):

This should not happen. There appears to be something wrong with this Windows system or something has modified the default installation options as others have suggested. (There are a number of reasons that may prevent Optional Features from being available. See this answer for some examples.)

I've now verified this to be true after completing a fresh install of Windows 10 version 1709 and then updating to version 1803. When updating to Windows 10 version 1803 without making any changes or installing any additional packages, OpenSSH Client was installed automatically as a result of the update.

Yes. It's possible to download OpenSSH directly from Microsoft's Win32-OpenSSH project on GitHub. See Alternate Installation Methods section below for details. This also makes it possible to install more recent releases of OpenSSH.

If running Windows 10 version 1709 (Fall Creators) there are two primary ways to install OpenSSH. If you're running a version of Windows 10 older than 1709, you will want to update to a newer version of Windows 10 via Automatic Updates. (It's also possible to use the Alternative Installation Methods listed below on older versions of Windows.)

Microsoft's instructions for installing the OpenSSH Beta in this version of Windows, which also covers additional steps for configuring and using OpenSSH, can be found here: Using the OpenSSH Beta in Windows 10 Fall Creators Update and Windows Server 1709

OpenSSH Client should already be installed after updating to Windows 10 version 1803. If you've verified you're running Windows 10 Version 1803 and OpenSSH Client is not installed, see the section below for Alternative Installation Methods.

Follow the instructions on the Win32-OpenSSH Wiki on Microsoft's Win32-OpenSSH GitHub Project. Pay close attention to the Wiki instructions and the version of Win32-OpenSSH as they change periodically.

However, this method is no longer recommended by Microsoft and the Microsoft Win32-OpenSSH Wiki explicitly states that this is "deprecated" (i.e. NOT RECOMMENDED), even though recent versions of the Chocolately package are released and available.

As per the original configuration, as described in the question, within an elevated PowerShell the following command Get-WindowsCapability -Online ? Name -like 'OpenSSH*' would have printed the following.

I've also tried looking for it under the standard Windows Features (Turn Windows Features on and off) as suggested by this answer and I do not see it listed. (I've even tried expanding all of the collapsible items just to make sure it wasn't hiding under IIS or something):

Unlike the feature when it was still in its beta form, it does not appear, in the legacy list of windows optional features. It only appears in the list accessed within Settings. The command to install OpenSSH Client and OpenSSH Server are identical between Windows 10 1709 and Windows 10 1803 by the way.

I have no idea why the second reboot was necessary, but after one reboot %SYSTEMROOT%\System32\OpenSSH\ had been added correctly to my $env:PATH, but I was still getting the "not recognized" error, but rebooting again fixed it.

I slightly modified the steps from Matt's blog because I already had some components of OpenSSH installed such as OpenSSH Authentication Agent (ssh-agent.exe) and OpenSSH Server (sshd.exe). I was only missing OpenSSH Client (ssh.exe):

After downloading and unzipping the archive into C:\Program files\OpenSSH I skipped the steps to install sshd.exe (PowerShell script install-sshd.ps1) and to install the Windows Services for sshd and ssh-agent, because these were already installed and working for me.

I tried installing 8.1.1 first, but it never worked. It just says "installation failed", and there is some cryptic error in one of the log files, which is hard to find. Others have posted about this in the forums.

Then I tried to install 9.1.1, and the install was a bit different. The first thing it does is tell you to accept and install .Net Framework. (Note that it doesn't even tell you which version it's going to install.) If you hit Accept, it brings you to a second, similar screen, where you must accept again. At this point, I refused because it was going to install .Net Framework 3.5, which I don't want. (All apps made for 3.5 can run on 4.5 or later, if the developer would simply specify that it can when building.)

Now I cannot install either version at all. If I try to install 8.1.1, it says I already have a later version installed, but I do not. There is no Vertica software visible anywhere in WIndows or in Program Files. Even worse, if I try to now install 9.1.1, it brings up an empty window with only this text at the top: "Microsoft .NET Framework required for Vertica Client Installer setup". There are no checkboxes or anything else in this window, so the only choice is to close it.

I had to give in and install .Net Framework 3.5 in order to complete the installation of client software version 9.1.1. But of course this latest version of Windows Pro won't install .Net 3.5 from by enabling it in Windows Features, nor by going to Windows Update, nor by downloading the web installer for it, nor by by downloading the 235 MB executable installer for dotNetFX35. So I had to download Windows Media Creator which allowed me to download an ISO image of Windows installer, from which I could then install .Net Framework 3.5 manually using a command like this:

So the first thing after Windows 10 1803 is installed afresh, is to install Visual Studio 2015 Update 3 immediately. Then install CUDA 9.1. After completion, CUDA installer will launch Experience in which you can safely install the latest 397.31 driver. If you are not sure, you can convince yourself that CUDA has successfully installed with VS even though there are many other directories of other VS versions by trying to new a project in VS. CUDA 9.1 is in the templates list of VS. Interestingly, Experience will complain there is no nVidia driver. Likewise, the CUDA 9.1 installer also installs NSight 5.4 which does not recognize the original 388.13, thinking the driver version is 0.0 and therefore fail the addWithCuda() function, even though the popups claim that NSight 5.4 works with 343.98+. So if you want to use Nsight to debug CUDA, you have to install the latest driver AFTER CUDA is installed. Since the problem I want to solve is to have CUDA integrate with VS, we can do installation on a simple basis (like old driver version or bare VS components). When the two agree with each other, we can then refine by installing new drivers, adding new features of VS and/or upgrading Nsight. After all, VS is not as delicate as CUDA.

I installed Windows 10 1709, CUDA and VS2015 previously (around half a year ago) without such problems. Yesterday, due to some accident I have to reinstall Windows 10. I downloaded the most recent installation (i.e., 1803) and these new problems bothered me a lot. So I am quite sure the problem comes with recent drivers. Anyone can easily reproduce the problem and the solution, including nVidia employees. So I hope they can fix it, because it is natural for a user to update drivers after the installation of the new Windows 1803 is done.