Enabling developer mode on Windows 10 Build build 10074 - windows

Windows 10 Insider Preview build 10074 has a known issue using the Settings application to enable developer mode. In this build, if you try Settings/Update & Security/For developers... the settings window suddenly closes.
Is there a workaround?

Yes, there's a work-around. In an administrator command prompt, type the following commands:
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock" /t REG_DWORD /f /v "AllowDevelopmentWithoutDevLicense" /d "1"
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock" /t REG_DWORD /f /v "AllowAllTrustedApps" /d "1"
Then reboot the machine to enable developer mode

Related

How to disable Fast Boot (Fast Startup, Hybrid Boot) only once by the next shutdown?

The problem is;
Our software (setup) detects that the computer (win10), it is running on, needs to be restarted due to file operations, other setups and so on. Then we are asking for restart now or later to continue.
If the user restarts the computer immediately or later, pending operations have been done, and all is ok. But if the user only does shutdown (from start menu) and later starts the computer up again (there is a Fast Boot) pending operations would not been done. It is clear, because of fast boot...
My question is; How can i programatically say windows to disable fast boot only once by the next shutdown? I don't want disable it completely and activate it after next startup. Is it possible?
Thanks to the comment of RbMm on the comments of the answer I did this script which disables the Hybrid boot and adds a command to the RunOnce key in the registry to reenable it on the next boot.
The batch needs to be run with administrator rights:
#ECHO OFF
%COMSPEC% /C reg add "hklm\SYSTEM\CurrentControlSet\Control\Session Manager\Power" /v HiberbootEnabled /t REG_DWORD /d 0 /F
%COMSPEC% /C REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce /v DisableHiberbootOnce /t REG_SZ /d "%COMSPEC% /C reg add """hklm\SYSTEM\CurrentControlSet\Control\Session Manager\Power""" /v HiberbootEnabled /t REG_DWORD /d 1 /F
As RbMm said the HLKM RunOnce key only it's executed if one administrator logins on the computer. To fix this I run on a GPO computer login script the command runonce.exe /explorer which runs the RunOnce scripts on the HKLM registry key without the need to log in as administrator.

Start->Run Dialog - "Run as Administrator" checkbox?

I'm trying to find if there's a registry key to enable the "Run as Administrator" checkbox on the Start->Run Dialog in Windows 7 (similar to the "Run in Seperate Memory Space" checkbox which can be enabled in the registry). At a couple of sites I remember I had this option, however on my current PC it's not enabled/visible.
If you know of a way to enable this checkbox via registry, or if it's available by a 3rd-party toolkit, please point me in the right direction?
I already know how to create a shortcut and set "Run as Administrator" on a specific application, and the "runas" command, I'm looking to enable the checkbox in the Start->Run command specifically in this instance.
Thanks.
Disabling UAC will give that option
To disable:
reg.exe ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableLUA /t REG_DWORD /d 0 /f
To re-enable
reg.exe ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableLUA /t REG_DWORD /d 1 /f
After restarting you will see the run box with admin privilege

VS2013RC requires IE10 but i need (not want) IE8

I've been evaluating the VS2013preview since its release and was keen to install the RC. The problem is we need ie8 for legacy testing as many customers out in the field still use it.
As a possible workaround would it be possible to either, skip or fool the install package into thinking its installed? or install ie10 and then drop back to ie8 after installation?
I appreciate there may be some areas of things like browserlink to ie that I cannot use but this is OK as I mostly use chrome for initial dev work prior to testing in the various browsers.
Credit goes to Jimmy here, but here's a hack to make it work:
#ECHO OFF
:IE10HACK
REG ADD "HKLM\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer" /v Version /t REG_SZ /d "9.10.9200.16384" /f
REG ADD "HKLM\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer" /v svcVersion /t REG_SZ /d "10.0.9200.16384" /f
REG ADD "HKLM\SOFTWARE\Microsoft\Internet Explorer" /v Version /t REG_SZ /d "9.10.9200.16384" /f
REG ADD "HKLM\SOFTWARE\Microsoft\Internet Explorer" /v svcVersion /t REG_SZ /d "10.0.9200.16384" /f
GOTO EXIT
:REVERTIE
REG DELETE "HKLM\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer" /v svcVersion
REG DELETE "HKLM\SOFTWARE\Microsoft\Internet Explorer" /v svcVersion
REG ADD "HKLM\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer" /v Version /t REG_SZ /d "8.0.7601.17514" /f
REG ADD "HKLM\SOFTWARE\Microsoft\Internet Explorer" /v Version /t REG_SZ /d "8.0.7601.17514" /f
GOTO EXIT
:EXIT
The problem is you're trying to use the same machine for developing and testing. Don't rely on the local copy of IE on your machine for testing a legacy browser, instead rely on virtual machine copies of Windows and run that specific browser.
If you want a quick & dirty way to test your stuff in specific versions of IE use the IETester as mentioned by others in the comments. http://my-debugbar.com/wiki/IETester/HomePage
You might want to consider simply using a virtual machine to run a copy of Windows with IE8 in it for your testing, since you don't really use it for day to day stuff anyways.
Microsoft announced yesterday that they are removing the requirement.
http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/4153040-remove-the-requirment-for-internet-explorer-10-to-

How to make Unicode charset in cmd.exe by default?

866 charset installed by default in Windows' cmd.exe is poor and inconvinient as compared with glorious Unicode.
Can I install Unicode by default or replace cmd.exe to another console and make it default so programms use it instead of cmd.exe?
I understand that chcp 65001 changes encoding only in the running console. I want to change charset at the system level.
After I tried algirdas' solution, my Windows crashed (Win 7 Pro 64bit) so I decided to try a different solution:
Start Run (Win+R)
Type cmd /K chcp 65001
You will get mostly what you want. To start it from the taskbar or anywhere else, make a shortcut (you can name it cmd.unicode.exe or whatever you like) and change its Target to C:\Windows\System32\cmd.exe /K chcp 65001.
Open an elevated Command Prompt (run cmd as administrator).
query your registry for available TT fonts to the console by:
REG query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Console\TrueTypeFont"
You'll see an output like :
0 REG_SZ Lucida Console
00 REG_SZ Consolas
936 REG_SZ *新宋体
932 REG_SZ *MS ゴシック
Now we need to add a TT font that supports the characters you need like Courier New, we do this by adding zeros to the string name, so in this case the next one would be "000" :
REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Console\TrueTypeFont" /v 000 /t REG_SZ /d "Courier New"
Now we implement UTF-8 support:
REG ADD HKCU\Console /v CodePage /t REG_DWORD /d 65001 /f
Set default font to "Courier New":
REG ADD HKCU\Console /v FaceName /t REG_SZ /d "Courier New" /f
Set font size to 20 :
REG ADD HKCU\Console /v FontSize /t REG_DWORD /d 20 /f
Enable quick edit if you like :
REG ADD HKCU\Console /v QuickEdit /t REG_DWORD /d 1 /f
Save the following into a file with ".reg" suffix:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Console\%SystemRoot%_system32_cmd.exe]
"CodePage"=dword:0000fde9
Double click this file, and regedit will import it.
It basically sets the key HKEY_CURRENT_USER\Console\%SystemRoot%_system32_cmd.exe\CodePage to 0xfde9 (65001 in decimal system).
For me, for Visual Studio 2022, it worked when I executed this ".reg" command.
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Console\C:_Program Files_Microsoft Visual Studio_2022_Professional_Common7_IDE_CommonExtensions_Platform_Debugger_VsDebugConsole.exe]
"CodePage"=dword:0000fde9
It is based on #Shaohua Li's answer: https://stackoverflow.com/a/24711864/2941313. It does the same thing but for different path (specifically for VS2022 console).

How to disable VS's just-in-time debugging completely?

Why I want to do this?
First, I never use it - spare me, this is going to sound ignorant, but I'm not interested. My debugging comes down to print and if statements. I've been doing it that way for a while, and have no interest in changing the way that works.
Second, a lot of programs which work until Visual Studio installation suddenly stop working upon it, just as Just-In-Time debugging starts to kick in.
Third, it's crashing some of my old programs (not my own, but programs I use) wherever a second screen is attached. Have no idea why this is happening.
Is there a way to turn it off completely?
I've disabled it in Visual Studio's options, but it still comes up with an error
An unhandled win32 exception ... Just-In-Time debugging this exception failed with the following error: No installed debugger has Just-In-Time debugging enabled. In Visual Studio, Just-In-Time can be enabled from ...
Check the documentation index for ...
(so in general, it's telling me that it isn't turned on)
How to disable it completely without uninstalling Visual Studio?
The way to do this is to select Debug > "Start without debugging (Ctrl+F5)" from the menu, instead of "Debug > Start (F5)".
You might also want to build your code in release mode when doing this - as the debug builds won't be of any benefit to you if you're not intending to debug them.
The issue of a windows program launching the debugger is not really one of changes in Visual Studio but is affected by changes in Windows which controls the JIT. You can build all code in release mode, but often want is just no debug pop ups. This is described in this article http://msdn.microsoft.com/en-us/library/k8kf6y2a(v=vs.80).aspx.
You need to issue the commands:
reg add "HKEY_CURRENT_USER\Software\Microsoft\Windows\Windows Error Reporting" /f /v "Disabled" /t REG_DWORD /d 00000001
reg add "HKEY_CURRENT_USER\Software\Microsoft\Windows\Windows Error Reporting" /f /v "DontShowUI" /t REG_DWORD /d 00000001
At that point you can run your programs without invoking the debugger. I do this in a batch file:
for /f "delims=" %%a in ('where reg 2^>nul') do #set theValue=%%a
if NOT "%theValue%."=="." GOTO :HaveReg
:: Might not have where - check again
for /f "delims=" %%a in ('reg /? 2^>nul') do #set theValue=%%a
if NOT "%theValue%."=="." GOTO :HaveReg
echo Unable to change registry keys to turn off program pop-ups
GOTO :DoneRegCheck
:HaveReg
reg add "HKEY_CURRENT_USER\Software\Microsoft\Windows\Windows Error Reporting" /f /v "Disabled" /t REG_DWORD /d 00000001
reg add "HKEY_CURRENT_USER\Software\Microsoft\Windows\Windows Error Reporting" /f /v "DontShowUI" /t REG_DWORD /d 00000001
:DoneRegCheck

Resources