[DISCUSSION] Windows 10 Technical Preview Build 9926

Thanks, just tested and it works.

Is there away to run cmd file as admin, so i can add tskill conhost ?

If there is than i will use this method.

 

i agree their all garbage.

 

It is now fbl.AWESOME.9934.

 

endbase

I have Edited Dos_Probie cmd and its works.

Code:

@set @jscript=1/*
@echo off

:: ### ADMIN CHECK..
 reg query "hku\S-1-5-19" >nul 2>&1 || (
    @cscript //e:jscript //nologo "%~f0" "%~f0"
    goto :eof
 )

:: ### BlUR AND ACCENT..
Start C:\Windows\System32\SetWindowCompositionAttribute.exe class Shell_TrayWnd accent 0 0 0 0
Start C:\Windows\System32\SetWindowCompositionAttribute.exe class Shell_TrayWnd blur true
Timeout /t 1
Tskill Conhost


:eof
// ### RUN AS ADMIN..
 */
 var strArg = WScript.Arguments(0);
 var objSH = WScript.CreateObject("Shell.Application");
 objSH.ShellExecute(strArg, "", "", "runas", "5");

So i will now use your method and Dos_Probie cmds.

 

Uninstall the KB3035129 from your system. But, that particular update is meant to fix that same bug.

 

This doesn't solve the problem.
After the next reboot it will be automaticly reoffered and reinstalled - no chance to get the new Build 9934.

 

is there still a cmd debug output with this method? also, can you post new instructions please cos I uninstalled and reverted it all? :'D

 

That is correct but not until you check for updates it will not re-install itself automatically. There is likely a clear notion you cannot download Build 9934 yet.

 

No there is no debug output with this method.

I will post new instructions if i can make it short.

 

how do i know the latest version
[h=2]10.0.10008.0.fbl_shell1_dev_mod.150129-1619 or 10.0.9934.0.fbl_awesome1501.150128-1644 [/h]is it the highest in build number or latest awesome version ???

 

You need to login to view this posts content.

 

These builds are not publicly available. You'll have to wait for official release or maybe someone will manage to download .esd and share it with us.

 

I'd rather deal with you any day of the week than some OS X fan... You at least likely know what you're doing...! Heh... Basically, though, I lost interest in spending inordinate amounts of time trying out various OS configurations--(which I spent eight very enjoyable years doing with my Amigas from the mid 80's-to-early 90's. AmigaDos/Workbench was like rubber in terms of how you could shape and use it.) Having gotten old and crusty, these days I'm far more interested in running 3rd-party software/hardware than in watching high how my OS will jump when I tell it to... But I can well remember the fun and fascination I had with doing that. You know you are getting old when you know an entire computing environment like the back of your hand and have to face the fact that it's gone extinct!

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

That really is murky as hell, hope they clear it up and fast. Leaves too much unknown.

 

I dont have a BlurDeviation entry, all I have is

Code:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\DWM]
"Composition"=dword:00000001
"ColorizationGlassAttribute"=dword:00000000
"EnableAeroPeek"=dword:00000001
"ColorizationOpaqueBlend"=dword:00000000
"ColorizationGlassReflectionIntensity"=dword:00000064
"ColorizationColorBalanceInactive"=dword:00000064
"ColorizationColorInactive"=dword:1a000000
"ColorizationColor"=dword:d900265c
"ColorizationColorBalance"=dword:00000064
"ColorizationAfterglow"=dword:d900265c
"ColorizationAfterglowBalance"=dword:0000000a
"ColorizationBlurBalance"=dword:fffffff6
"EnableWindowColorization"=dword:00000001

so I guess I can merge your entry

followed that but I have no Glass, so where did we go wrong? Maybe I put TaskBlur.cmd in the wrong Start-up Folder? C:\Users\matt\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup

 

But Gabe has said to not touch anything in the registry because we can lose the next updade

​

 

You need to login to view this posts content.

 

You need to login to view this posts content.