ulbelli khristie derylin

0 views

Skip to first unread message

Faustina Bartsch

unread,

Aug 2, 2024, 10:46:34 PM8/2/24

to derrohunve

Windows 10 April 2018 Update[1][2] (also known as version 1803[3] and codenamed "Redstone 4") is the fifth major update to Windows 10 and the fourth in a series of updates under the Redstone codenames. It carries the build number 10.0.17134.

The first preview was released to Insiders on August 31, 2017. The final release was made available to Windows Insiders on April 16, 2018, followed by a public release on April 30, and began to roll out on May 8.[4][5]

The update has reached end of service on November 12, 2019 for Home, Pro, Pro for Workstations and IoT Core editions.[6] The Enterprise, IoT Enterprise and Education editions would have originally reached end of service on November 10, 2020, but this was postponed to May 11, 2021 due to the "global health crisis", in reference to the COVID-19 pandemic.[7][8][9]

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.

Thank you for your reply Sharon. It seems like Windows 10 1803 has been released and the issue remains. My computer is out of commission because I don't want to waste time reinstalling Windows 10 1709 with all my software while waiting for the fix to come out for 1803. Searching the interwebs doesn't bring up a solid lead and looks like I am at a loss. Please advise if there is any information regarding this issue.

Sharon, it turns out Microsoft pulled the update the last day it was to be released. Microsoft announced they will be releasing the update on April 30th for manual download, and rolling it out on May 8th. I have not revisited this issue because of the amount of work it would take to reinstall windows on my main machine just to check if the issue is actually resolved. It would be nice to know if there was any concrete information regarding this issue before doing this. Thank you.

This will become a major problem when Windows decides it's going to auto update my system to 1803 which has caused the biggest mess thus far. Besides the other post that was mistakenly marked as answered, there isn't much information regarding this issue. On top of the fact that VLAN tagging your NIC is niche, I wonder if anyone else is experiencing this issue.

The moment SW 23.2 is available and published on our Intel Download Center this thread will be updated with a link to the Intel Ethernet Adapter Complete Driver Pack as it is the first download record that we publish for each SW release.

This release brings support for Windows 10 Redstone 4 (RS4). If you updated to Windows 10 (RS4) prior to this release and experienced problems creating ANS Teams and VLANs, please update to SW release 23.2.

I am sorry to hear what happened. We need some information from those that are still having issues following an upgrade to Windows 10 (RS4).For those experiencing problems please help us reproduce these issues by sharing the following information.

I am not sure regarding my actual previous Windows version. I was out of office working via RDP when windows told my that I have to reboot to install an update.After reboot windows newer cam online again. Back in office I realized, that the formerly configured VLANs where not working. Therefore my PC newer gone online again. No connection at all.

I tried with and withoud prior configured VLANs. In one step I removed the drivers completely and even disabled "build in network cards" in bios. Windows Reboot, delete "old" cards, reboot, enabled "build in network cards" and installed 22283 (complete driver pack)

I am not able to create support tickets. There seems to be a problem with your ticket system. Can you access my profile and see my email? You could send me an email and then I will send you the SSU-file.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

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'm using Eset Internet Security version 11 with latest build. I upgraded my Windows 10 just 4 days back from Windows 10 version 1709 to 1803 build 17134.1. Last 2 days Eset was alright but it started showing an warning alert from last 2 days.