2020. 3. 6. 15:02ㆍ카테고리 없음
Contents.Overview The first release of WSL provides a -compatible kernel interface developed by Microsoft, containing no code, which can then run a on top of it, such as that of,. Such a user space might contain a shell and command language, with native GNU/Linux command-line tools (, etc.), programming language interpreters (, etc.), and even graphical applications (using a at the host side).The architecture was redesigned in WSL 2, with a Linux kernel running in a lightweight virtual machine environment.Introduction and availability When introduced with the on August 2, 2016, only an Ubuntu image was available. The, released on October 17, 2017, moved the installation process for Linux distributions to the, and introduced images.WSL is available only in 64 bit versions of Windows 10 from version 1607. It is also available in Windows Server 2019.Microsoft announced WSL 2 on May 6th, 2019, which features a completely new VM-based backend (based in a subset of Hyper-V features) in lieu of the prior system call adaptation layer, planned for release through the Windows Insider program in June 2019.Development Microsoft's first foray into achieving Unix-like compatibility on Windows began with the, superseded by via /, which was eventually deprecated with the release of. The technology behind Windows Subsystem for Linux originated in the unreleased, which enabled some applications to run on. It was first made available in build 14316.Whereas Microsoft's previous projects and the third-party had focused on creating their own unique environments based on the, WSL aims for native Linux compatibility. ^ Craig Loewen (6 May 2019).
Windows Command Line Tools For Developers. ^ mscraigloewen. Windows Command Line Tools For Developers. 14 May 2019. Gerwitz, Mike. Retrieved 8 April 2018.
Harsh, Mike (30 March 2016). Building Apps for Windows. Finley, Klint (30 March 2016). Kirkland, Dustin (30 March 2016). Ubuntu Insights. Hammons, Jack (9 April 2016). Yegulalp, Serdar (12 May 2017).
Retrieved 16 September 2017. ^.
Windows Command Line Tools For Developers Blog. 10 July 2017. Retrieved 11 August 2017. Windows Command Line Tools For Developers. Retrieved 7 March 2018. Retrieved 9 March 2018. ^.
Retrieved 13 November 2016. Bright, Peter (6 April 2016).
Aul, Gabe (6 April 2016). Windows Experience Blog.
Windows Subsystem for Linux. Retrieved 22 April 2018.
Microsoft Ignite (2 October 2018), retrieved 7 May 2019. Jack Hammons (22 April 2016).
Windows Subsystem for Linux blog on. Jack Hammons (15 June 2016). Windows Subsystem for Linux blog on. Jack Hammons (8 November 2016).
Windows Subsystem for Linux blog on. Windows Developer feedback (Microsoft/UserVoice). Retrieved 10 September 2018. Retrieved 10 September 2018.
Windows Developer feedback (Microsoft/UserVoice). 15 September 2016. Retrieved 10 September 2018. Michael Larabel (12 October 2018). Phoronix. Michael Larabel (5 November 2018). Phoronix.
Loewen, Craig (26 July 2019). Archived from (html) on 26 July 2019.
Retrieved 26 July 2019. In this new update we’ve added the ability to start using global config options for WSL. These options are targeted towards power users who want to further customize their WSL experience.
Hillis, Ben (25 July 2019). Archived from (html) on 26 July 2019. Retrieved 26 July 2019. Windows Command Line Tools For Developers. Retrieved 24 June 2019. Windows Command Line Tools For Developers. Retrieved 24 June 2019.
Retrieved 23 September 2019.External links Wikimedia Commons has media related to. blog. on Microsoft Docs. on. Brown, Pete (22 July 2016). Windows Developer Blog.
If you asked a knowledgeable computer user how to uninstall Internet Explorer completely in Windows, they would likely advise you not to do that because IE is part of Windows and some features require the IE files be present or there would be crashes and other weird problems. The same principle applies to to DirectX. Simply put, DirectX is a Windows technology that enables higher performance in graphics and sound when you’re playing games or watching video on your PC. Even if you CAN uninstall DirectX completely, it’s almost guaranteed you that you will face problems on your computer by doing so.For example, if you uninstalled DirectX and tried to launch Windows Live Messenger, there will be an error popup “This application has filed to start because DSOUND.dll was not found. Re-installing the application may fix this problem”. That’s because the dsound.dll is a part of DirectX which adds functionality for Direct Sound and Messenger requires it. Logging in to will make the screen and advertisements keep on flashing.
As for computer games, anything that relies on DirectX wouldn’t run, which is most games available today.So, if you have problems when trying to play a game or watch a video and know that it has something to do with DirectX, the first thing we would suggest is to download the and perform a re-installation. This will replace any missing files. However, if re-installation fails or doesn’t fix the problem, your last resort would be to uninstall DirectX and then try installing again. Here’s a few different ways on how to try and uninstall DirectX. Note: After completely removing it from your computer, you won’t be able to re-install DirectX, so this isn’t the ideal way to go about it.
If you try running the dxwebsetup.exe, you’d get the error “An internal system error occurred. Please refer to DXError.log and DirectX.log in your Windows folder to determine the problem.” Weirdly, both log files cannot be found in the Windows directory. What you need to do is to rollback to the original DirectX from the Windows setup disc first, then install and update DirectX to the latest version. There are a few tools and scripts around which are able to help you uninstall DirectX or rollback to the original DirectX from Windows installation CD.1. A Simple Registry HackThe first trick to try and get DirectX to re-install involves a small change in the registry. This does the simple job of fooling Windows into thinking it has an older version of DirectX currently installed and therefore will allow the latest version to be installed again over the top. This is the easiest fix to try and doesn’t need the use of third party software.
Follow these simple steps:1. Run Regedit by pressing Win key+R to get the Run Box and type Regedit, then press enter.2. Locate the following registry key:HKEYLOCALMACHINESOFTWAREMicrosoftDirectXYou should then see a value called “Version” with a data value of 4.3. Simply double click on Version and change the number from 4.
Then close the registry editor.If you’re not someone who likes to poke around in the registry, simply download one of the.reg files from below, and double click to import one of the above numbers into the registry for you. Now download and run the, and it should re-install.
This could also work in Windows Vista and 7 because the 4. Version number is the same.
We haven’t fully tested it though on these operating systems, so do it with care and at your own risk.2. DirectX 9 UninstallerThis uninstaller uses your original XP CD and restores the original DirectX 8 files from it. DirectX 9 uninstaller extracts the DirectX 8 files from the Driver.cab in the i386 folder on the CD into a folder on your hard drive called C:DXTEMP. Extract the DirectX 9 Uninstaller files and then execute the UnDx9.bat file. That will start the process to uninstall and replace the DirectX 9 files. The UnDx9 Uninstaller batch file MUST BE USED IN SAFE MODE because DirectX files will be locked in normal mode.
Directx
The tool can only uninstall DirectX 9 from Windows XP and 2000.We have three more methods to uninstall or rollback DirectX on page 2.