New Email out from Turing Phone

New Email out from Turing Phone
turing phone
Welcome to the latest in Turing Phone™ news!First of all, thank you for your interest in the Turing Phone™.

We’re overwhelmed by the response and support you’ve given us since announcing our July 31st pre-order date. We’re working through your questions and will reveal much in the coming weeks.

Watch your inbox and receive the news first. Next week, we’ll be sharing pre-order details and unveiling new product photography.

Last week our CEO, SYL, stopped by the Mashable office to talk about the next evolution of phones, the cipher phone, as well as give a sneak peek of the Turing Phone™. In case you missed it, take a look:

Read Article
Thanks again for joining us in building the future. Patrons and supporters, like you, inspire us to keep challenging the status quo and pushing the limits of technology.Stay tuned for more exciting news,

– TRI Team

P.S. Forward to a friend and show them the future.

Run elevated command prompt (CMD)

The quickest way to run an elevated command prompt from windows xp all the way through to Windows 10, is to simply right click and ‘Run as Administrator’ from the start menu, see below

Click on the start menu, or press the WIN key, then simply type (win vista+)  CMD
Right click on cmd.exe and select, run as administrator Run elevated command prompt (CMD)


If that does not for some reason work, or you cannot get into your start menu, try pressing WIN + R and typing CMD, then enter:

 runas /noprofile /user:Administrator cmd

This will prompt you for your admin password
run box windows elevate command prompt

Create new user via cmd

How to create new user via cmd (command Prompt)

create new user via cmd

Below are the quick steps to take if you are in the situation where you need to create a new pc user from command line. The example below is for creating a user named nick, with admin privileges.

Open up an elevated command prompt:
Type the below, exchanging *nick* ad *password* with your own username and password.

net user /add *NICK*  *password*

To give this user admin privileges;

net localgroup administrators *NICK* /add

Getting the path of AppData using PowerShell

Getting the path of %AppData% using PowerShell + $env: usage

There are 2 ways to find the folder location of AppData on a  PC, and to check appdata path.

The first method uses the simple $env: command. This command has long been used by C# users to make multi platform software, in the case where your AppData or any other environmental variable may be living somewhere other than the normal factory set location.

Simply open up powershell and type:


Getting the path of %AppData% using PowerShell + $env: usage

Method 2 is basically doing the exact same as above, but this time using a call and answer approach:

Get-Childitem env:APPDATA | %{ $_.Value }

path of %AppData% using PowerShell + $env:  call

Below are some extra $env: variables that you may find useful;

Name                           Value
----                           -----
TEMP                           C:\DOCUME~1\bob\LOCALS~1\Temp
SESSIONNAME                    Console
PATHEXT                        .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.PS1;.PSC1
USERDOMAIN                     WINGROUP
SystemDrive                    C:
APPDATA                        C:\Users\bob\Application Data
windir                         C:\WINDOWS
USERPROFILE                    C:\Users\bob


Windows 10 release set for July 29th 2015

After a batch of updates over the weekend, Windows is now providing more info on the long awaited FREE windows 10 upgrade
Windows 10 release set for July 29th 2015

Windows 10 release set for July 29th 2015

The popups, now appearing on some windows 7 and 8 PC’s are causing quite a stir. With some people on reddit calling it both ‘intrusive’ and ‘malware-like’ 
It would appear that it is KB3035583 that installs this notification, but that requires Windows 7 SP1 or Windows 8.1 to function correctly, at the bottom of the article we have included a step by step guide in forcing this update in order to be able to reserve your own copy of Windows 10

Below, the sirst 5 screens, then taking you through to the final offer, of ‘reserving Windows 10’

win101 win103win102  Windows 10 release set for July 29th 2015 Windows 10 release set for July 29th 2015 Windows 10 release set for July 29th 2015 Windows 10 release set for July 29th 2015

If you are still looking to get a hold of the update supplying this notification then Reddit user FearGX_ explains that you can force the update to do its thing. We’ve reformatted his instructions below.

  1. Open the Control Panel, choose Administrative Tools, and then fire up the Task Scheduler.
  2. Expand Task Scheduler Library, then Microsoft, then Windows, and finally scroll down to expand Setup.
  3. Click the folder GWXTriggers and on the far right hit Run.

Again, this will only work if you’re running a legitimate copy of Windows 7 SP1 or Windows 8.1, have KB3035583 installed, and have all the latest updates.

Quick and dirty way to transfer or recover FSMO roles

Here are the basic steps you can use to transfer or recover FSMO roles during or after migration;

Without going into detail about how this process works, or what it does, If you have just migrated a new Server and are ready to make it the live master for the forrest and domain, simply open up a command prompt (CMD) and enter the following lines in one after the other;

transfer or recover FSMO roles

Connect to server *New Server Name*
Seize infrastructure master
Seize naming master
(if success – continue to the below)
Seize PDC
(Server “*Server Name*” knows about 5 roles)
Seize RID master
Sieze schema master

Finito. (<– dont type that!)

Why do we need to transfer FSMO Roles, or what are they anyway!?

Because an Active Directory role is not bound to a single DC, it is referred to as a Flexible Single Master Operation (FSMO) role. Currently in Windows there are five FSMO roles:

Schema master
Domain naming master
RID master
PDC emulator
Infrastructure master

And that is your FSMO roles all transferred over using simple command line. Please keep your eyes peeled for further posts looking deeper into each of the FSMO Roles,

Check if PC is joined to the domain

Here is a quick way to check the health of a PC joined to a domain controller. This is very useful if you need to do a quick check in the first instance of diagnosing a trust relationship issue.

pc is joined to the domain

Here are the steps to check if a pc is joined to the domain using Powershell:

1) Open up a powershell console

2) Type or copy/paste the following, replacing the *dc mane* with your networks domain controller

Test-ComputerSecureChannel –Server *dc name* -Verbose

3) check results, If it comes back with red text it is a pretty good indicator that there is some form of problem going on, however if it returns “The secure chanel between ‘*’, ‘*dc name*’ and ‘*domain*.local’ is alive and working correctly”  then you can continue investigating your problem knowing that the PC is nice and safely connected to the domain.

For troubleshooting Trust Relationship issues with a Microsoft Domain, please keep your eyes pealed for part 2

Set server to automatically update time

If you have ever been in the situation where a time server or an old server will just not keep in sync, perhaps due to a CMOS battery error, or simply old hardware, then this cmdlet is for you.

Here is how to set a server to automatically update time;

automatically update time

Open up a command prompt and copy/paste the below:

w32tm /config /manualpeerlist:””,0x8 /syncfromflags:MANUAL
w32tm /config /update
net stop w32time
net start w32time
w32tm /resync /nowait

All that this is now doing is setting the clock to update automatically from a web time server, the servers we are using are the public pool 1, 2 and 3 at
We stop and start the time services, and then tell it to resync with the new settings.

Windows Update stuck 3 of 3 – Can’t use PC

It would seem that the last batch of updates from Microsoft around the 12th-14th May 2015 have been causing quite a few PC’s to hang stopping at Update 3 of 3.

This so far looks like it is only affecting Windows 7 Pro X64 based PC’s

As with most IT Professionals, we would never suggest performing a Hard shut-down to your PC, unless there really is no other option, however it does look like in this case this is the only way to fix this particular ‘Stuck Update‘ issue.

If your Windows Update  stuck: windows update stuck 3 of 3

Option 1)

This seems to be working for 50% of users encountering this issue, if it does not work then proceed to option 2.

Option 2)

Step 1) Hold down the power button on your PC for 10+ seconds,
Step 2) Restart PC by repressing the power button
Step 3) If confronted with a windows error ‘Your PC did not shut down normally’ screen, select “Start Windows Normally”

Out of the 7 PC’s we have now done this to, all in different environments, we are yet to see any errors or corruptions caused by this. We are continuing to look into which update specifically caused this and why, and so check back later to keep yourself updated.


For further reading see this Reddit thread.