Question: Standard corporate environment, forcing clients to got through a proxy server via a proxypac. In the OSX configuration is in the following format:

```
http://www.proxy.server.name:8080/proxy_pac_path_to_package.pac

```

Trying to connect via CLI, for a homebrew install, and used (so far) the following options:

```
export http_proxy=http://www.proxy.server.name:8080/proxy_pac_path_to_package.pac

export http_proxy=http://www.proxy.server.name:8080

export http_proxy=http://myusername:mypasswd@www.proxy.server.name:8080/proxy_pac_path_to_package.pac

export http_proxy=http://myusername:mypasswd@www.proxy.server.name:8080

```

with mypasswd special characters being mapped into their hex code, and with username using either the "simple" form, or the entire AD path, or the email, etc.

None of the above worked. Any idea about what I may be missing, from one's own experience through non-obvious things?

Answer: 
This isn't a solution for you, unfortunately. I have the same issue and haven't been able to find a solution, hack, or fix anywhere. I ended up rolling back to Windows 10 Pro version 1511 and selecting the "defer upgrades" option in *Updates*, *Advanced Options*, to put off receiving upgrades for as long as possible with the hope that these bugs will be worked out by the time Microsoft forces the upgrade on us. Note that this is only available in the Pro version. Doing this does not prevent any security updates. I wish I could be of more help.
OK, this is a thought experiment which I know is probably in breach of the advice about answers.

It appears that the relevant registry settings are (see relevant registry settings in [Windows 10: Backup and Restore Folder View Settings in Windows 10](http://www.tenforums.com/tutorials/17777-folder-view-settings-backup-restore-windows-10-a.html)).

* HKCU\Software\Microsoft\Windows\Shell\BagMRU and
* HKCU\Software\Microsoft\Windows\Shell\Bags.

In my case I appear to have over 100 entries within these keys which I assume is because I use sub-folders in my Library all the time and I am continually trying to set the views to what I want them to be.

So my imaginary (i.e. untested) steps would be:

1. Export copy of current values of those registry keys to files (you could use the bat script created by Shawn Brink from the reference above to do this)
2. Close Windows Explorer
3. Delete those settings from your registry using lines below in a cmd window:

```
Reg Delete "HKCU\Software\Microsoft\Windows\Shell\BagMRU" /F

Reg Delete "HKCU\Software\Microsoft\Windows\Shell\Bags" /F

```
4. Open Windows Explorer, which should get Windows 10 to rebuild all views to defaults
5. Export the default registry settings for the two keys above to new files
6. Using Windows explorer change to your Documents folder (or any folder you choose) and configure view settings to the way you like them then Save the settings for that folder
7. Export registry settings for those two keys again
8. Use a text editor to compare the changes between the default registry settings and the new ones (I would use `diff` and `vi` to accomplish this, but then I am an old unix hack - nb not 'hacker')
9. Apply these changes to all sub-keys that have the same settings as the old sub-key before you changed it.
10. Close Windows Explorer and delete the registry settings again
11. Import these modified files back into the registry
12. Open Windows Explorer again

This will probably work until you add a new folder to your library when it will revert all views back to the default settings again. Urrggghhhhh