# Support \`language:generic\` and \`language:minimal\` in Windows **URL:** \ **Category:** Feature Requests\ **Tags:** travis-build, windows\ **Created:** [December 10, 2019, 2:43am UTC](https://travis-ci.community/t/support-language-generic-and-language-minimal-in-windows/6377 "2019-12-10T02:43:12Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\ **Post date:** [December 10, 2019, 2:43am UTC](https://travis-ci.community/t/support-language-generic-and-language-minimal-in-windows/6377/1 "2019-12-10T02:43:12Z")
Currently, Windows accepts `language: shell` – which has no default script, but doesn’t accept `language: generic` and `language: minimal` – which are the designated configurations without a default script. This has been creating roadblocks for me ([example](https://github.com/native-api/test_travis/commit/a443c39a90c14e934c816d136fe6c2387b134bb8), but generally, I overwrite unsuccessful attempts with forced pushes) if I wish to check things in all 3 OSes and need `language: generic` functionality in Linux. * * * Since I’m already getting a Windows VM for `language: generic` and `language: minimal`, VM type selection logic isn’t an issue here and it’s sufficient to patch `travis-build`. I don’t care if `generic` and `minimal` would yield the same VM image (there’s only one kind of Windows image anyway AFAICS). > ---
**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\ **Post date:** [December 12, 2019, 8:43pm UTC](https://travis-ci.community/t/support-language-generic-and-language-minimal-in-windows/6377/2 "2019-12-12T20:43:48Z")
The PR has just been merged. Many thanks!