# Disable automatic detection of nuget.config
**URL:** https://www.finalbuilder.com/forums/t/disable-automatic-detection-of-nuget-config/5495
**Category:** Feature Requests
**Created:** [July 25, 2016, 8:27am UTC](https://www.finalbuilder.com/forums/t/disable-automatic-detection-of-nuget-config/5495 "2016-07-25T08:27:29Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@catenalogic](https://www.finalbuilder.com/forums/u/catenalogic)
#### Post date: [July 25, 2016, 8:27am UTC](https://www.finalbuilder.com/forums/t/disable-automatic-detection-of-nuget-config/5495/1 "2016-07-25T08:27:29Z")
I am testing NuGet 3.5 beta 2 because I am setting up [asp.net](http://asp.net) core sites in Continua CI. There is a bug (or maybe it’s by design, you never know) in NuGet where it fails to restore packages when a config file is specified:
[https://github.com/NuGet/Home/issues/3208](https://github.com/NuGet/Home/issues/3208)
I have tested this, and it looks like NuGet can automatically detect the config now (and when not specifying the config explicitly via the command line), it works. If you explicitly specify it, it fails. Continua CI has a nice feature where it automatically tries to detect the config file (because this was required for older NuGet clients). However, now this same feature is shooting us in the foot.
My proposal is to either add an additional checkbox (default to true if config file is not explicitly specified to not cause breaking changes) that checks whether to search for a default config or not.
---
### Author:  [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)
#### Post date: [July 26, 2016, 9:11am UTC](https://www.finalbuilder.com/forums/t/disable-automatic-detection-of-nuget-config/5495/2 "2016-07-26T09:11:13Z")
Hi Geert,
Thanks for reporting this. I’ll add this option for the next build.