Windows 10 1703 Download

[Dinah Lianes]

Windows10 Creators Update[1] (also known as version 1703 and codenamed "Redstone 2") is the third major update to Windows 10 and the second in a series of updates under the Redstone codenames.[2] It carries the build number 10.0.15063.

The first preview was released to Insiders on August 11, 2016. The final release was made available to Windows Insiders on March 20, 2017, followed by a public release on April 5 via Update Assistant, and began to roll out on April 11.[3]

The update has reached end of service on October 9, 2018 in the Semi-Annual Channel.[4] The Enterprise and Education editions have reached end of service on October 8, 2019.[5][6] Support of this update on Surface Hub devices was available until March 16, 2021.[7]

I am currently stuck to Windows 10 1703. As a result I get the cryptic 0x80073CFD error when I try to start Linux. This is Windows' way of telling the user that their version of Windows is too old for the requested Application.

As there are blog posts and such where people write about running Linux on Windows 10 1703, there must be appx-packages out there, that will run on Windows 1703. Can anyone provide me with a source for such (outdated) packages?

I specifically ask for a source for appx-packages that will run on Windows 10 1703. That information is not provided in the answers to the referenced question, b/c the user does not need them, b/c they are on Windows 10 1709.

I specifically ask if the most recent versions, i.e. the ones mentioned in the referenced question, can be hacked to not require version 1709 anymore. That information is not provided in the answers to the referenced question, b/c the user is on Windows 10 1709.

The only WSL instance that is compatible with your system is Ubuntu 16.04 by the way. You can perform a forced upgrade to 18.04 but I cannot suggest performing an upgrade using that method. If you need an offline method to install Ubuntu 16.04 WSL on Windows 10 v1703 you can use lxRunOffline v1.1.0.

The first time you run Bash on Ubuntu on Windows, you'll be prompted to accept Canonical's license. Once accepted, WSL will download and install the Ubuntu instance onto your machine, and a "Bash on Ubuntu on Windows" shortcut will be added to your start menu.

There are various ways of making a Windows 10 bootable USB stick. You can even do it in Linux - it is not difficult. There is a description of how to do it here: How to Create a Bootable Windows 10 USB in Linux

Use an iso of 1703 with a tool like YUMI to create a boot-able flash drive with your choice of OS with or with out UEFI. You can also load multiple images on to one drive and select the desired OS at boot. There are several products available online that will do this.

I managed to create a Windows 10 bootable 1793 USB by RUFUS. It had all the different versions of Windows 10 built in. I chose the one I wanted. I then booted the system I was trying to fix and the bootrec /fixboot worked. Unfortunately It still would not boot.

Trying to update Windows 10 Pro x64 version "1607" to "Creators Update 1703". I have attempted this update repeatedly in a variety of ways: via Windows Update, via an update 1703-specific installer, and via an ISO-based installer.

I have updated all my Intel networking software to what appears to be the latest/greatest, via the "Intel Driver Update Utility v2.8.2" (which installed wireless driver 19.70.0.5, bluetooth driver 19.71.0.2), and something Intel calls the "Intel Network Connection Install Wizard" (which installed ethernet/gigabit driver 22.4.0.1). All of these versions are listed as "latest" on the various relevant Intel driver support/download pages.

This appears to be a show-stopping incompatibility as far as Creators Update 1703 is concerned. I can't proceed with that Windows update, and while it is hard to imagine I am the only person having this problem, I can't find anything definitive about this on the web.

So, my current situation: intractable driver incompatibility, can't update Windows 10 (and additional Windows 10 updates are now backing up behind Creators Update 1703), and none of Microsoft, Intel, or Gigabyte is prepared to address this problem.

Based on your error, I can recommend for you to post to our /community/tech/wired Wired Ethernet Support Community. Or for a more personal interaction, you may also contact our support team for assistance.

Intel's latest 8260 driver download 19.70.0.5 supplies NETwtw06.sys and NETwtw06.dat instead. Windows Update 16251 changed drivers to its older, incorrect 19.50.1.6 NETwtw04.sys and NETwtw04.dat files.

The company that build my system (Puget Systems; Auburn, WA USA) appears to have identified a workaround to this problem. They have documented the workaround in a "help" article posted on their website:

Recap: Windows 10 Creators Update 1703 would not install on my Intel X99-based system, which uses a Gigabyte GA-X99-Designare EX (rev. 1.0) motherboard, with the following error message generated during installation:

A potential source of confusion: my processor only has 10 cores to begin with, so the notion that 16 cores is some sort of magic maximum is mistaken. Out of an abundance of caution, I reduced my system to 6 cores (out of 10).

Of note: there is that pesky file again, Netwtw04.sys... this is perhaps why Windows 10 Creators Update 1703 was refusing to install, Microsoft knew something we did not, but they were clumsy/not-very-informative about it. I am going to give Microsoft the benefit of the doubt.

Conclusion: Something about Gigabyte's (Intel) wireless networking driver is not compatible with Windows 10 Creators Update 1703. The driver supplied by Gigabyte is an older version of the driver. Somewhat mysterious is the fact that installing v19.70.0 direct from Intel did not rectify this problem, can't explain this.

Note to Intel: I never touched any of the "wired" driver components in the course of applying this workaround. The problem would seem to be in the wireless driver after all, albeit not the latest/greatest version of that driver from Intel.

Reducing the number of processor cores worked around the NETwtw04.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED problem, which Creators Update 1703 knew would be there, so Creators Update 1703 could proceed, delete NETwtw04.sys, and finish updating successfully.

Anyway, both Windows 10 Creators Update 1703 and Intel v19.70.0 seem happy together, on a full manifest of 10 cores (for my particular model of processor). Apparently I had to get Creators Update 1703 to complete first though, by disabling cores.

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.

However, before upgrading to W11, I strongly suggest that you use the free Macrium Reflect software to make a system image and bootable rescue media to access the image in case you ever have to go back to W10 after the default 'go back to W10' period expires. I think you have 10 days to go back to W10 in case you don't like W11, or it doesn't work right on your notebook.

I would make a system image of your current W10 installation prior to updating to W11, so you can easily reinstall W10 in the future. I used the free Macrium Reflect software to do that, under the Backup at Home section.

I used the first procedure to do an in-place upgrade an old HP Elitebook 6930p notebook made in 2010 to W11, and I was able to keep my old Office 2010 Starter program that came with the notebook when it had W7 on it, along with all of my other programs, files and settings.

I want to know, if I install Win 11 in those ways you mentioned, what will happen to my Windows Activation as my current genuine windows is OEM activated. I've seen many ways internet, but no one tells about OEM activation. I think you could clarify this.

I am using Excel 2007. This morning I installed the Windows 10 upgrade 1703. Now the VBA in my Excel spreadsheets is blocked from running. I get the message "Cannot run the macro 'macro name'. The macro may not be available in this workbook or all macros may be disabled." I get the same result no matter which macros I run.

Checking the VBA editor, all macros are present in the document. VBA routines don't run via the editor. The "Design Mode" control is yellowed out and gives me the same kind of protection message when clicked.

I checked the permissions in the Trust Center and trusted locations only to find they are still the same as they have been for the past years. I also search the Windows 10 settings to see if there is another setting which might be new to this upgrade. I find none.

The reference file has these items checked; VB for Applications, MS Excel 12 Obj Lib, OLE Automation, MS Office 12 Obj Lib, and MS XML, v6.0. Seems like all the excel applications are covered. Then there is the Personal.xlsb file. I did not have one so I created one. Macro loaded in it runs fine, but my others do not.

3a8082e126