Skip to main content

Change Boot Order in Microsoft Surface Pro 3 and Above Devices.

You can change the Boot Order of Microsoft Surface Pro 3 and above, use the following sequence of commands:


Step 1:Shut down your Surface.
Step 2:Once Surface has turned off, press and hold the volume-up button.
Step 3:With the volume-up button held down, press and release the power button.
Step 4:Continue holding the volume-up button until the Surface logo no longer appears on the screen.
You should now see the Surface UEFI. Do one of the following:
  • Surface Pro 3 and Surface 3: Go to Step 5 below.
  • Surface Pro 1 and Surface Pro 2: Skip to Step 9 below.
Surface Pro 3 and Surface 3:
Step 5:Select Configure Alternate System Boot Order.
Step 6:Do one of the following:
  • Surface Pro 3: Select USB > SSD
  • Surface 3: Select Network > USB > SSD.
Step 7:Select Exit Setup.
Step 8:Select Yes to save the configuration and restart Surface.
Surface Pro 1 and Surface Pro 2 (optional for Surface Pro 3)
Step 9:Select Secure Boot Control.
Step 10:Select Disable. This will allow Surface to search for an alternate device to boot from aside from your SSD.
Note
This may affect the look of your Surface splash screen.
Step 11:Select Exit Setup.
Step 12:Select Yes to save the configuration and restart Surface.

Comments

Post a Comment

Popular posts from this blog

Connecting Nodejs to SQL Server with Knex ORM - Part 1

Normally we connect Nodejs to the databases like SQLite, MongoDB, Postgres etc . In this multiple part post, I am going to show you, how we can connect Nodejs with Microsoft's SQL Server using Knex and run CRUD operations. 1. Installation of required packages In order to connect Nodejs to SQL Server with Knex, we will need following node packages installation: i. npm install knex ii. npm install mssql Once the packages are installed, we can write the following code to connect: //Code to KNEX connection settings. var knex = require('knex')({ client: 'mssql', connection: { user: 'sa', password: 'pwd', server: 'localhost', database: 'Test' } }); //Code to query the Table DEPT knex.select("*").from("dept") .then(function (depts){ depts.forEach((dept)=>{ //use of Arrow Function console.log({...dept}); }); }).catch(function(err) { ...
Post a Comment
Read more

SQLServer Error: 15404, Could not obtain information about Windows NT group/user Error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)

If we encounter this error "SQLServer Error: 15404, Could not obtain information about Windows NT group/user Error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)" in SQL Server in which the job fails because of the user account related problem, then we need to take the following steps to make it work: a. Go to SQL Server Agent. b. Then select the job which is giving error and not running successfully. c. Then choose properties and in the General Tab, change the owner to "SA" or any account that has the administrative privileges. The problem will be resolved.
1 comment
Read more

MAX pool size reached in ASP.NET

If you are handling large databases and big application(s) that are running on servers in a cluster, then probably this error might have occurred. In an ASP.NET app, we can use connection pooling that helps to share the connection between multiple request(s) rather than creating more connections. The settings relating to connection pool are defined in web.config file. Max pool size reached error in ASP.NET occurs, when the number of connections go beyond the maximum defined limit in Web.config file. Following are the various settings of the Connection Pooling: Name Default Description Connection Lifetime 0 When a connection is returned to the pool, its creation time is compared with the current time, and the connection is destroyed if that time span (in seconds) exceeds the value specified by  Connection Lifetime . This is useful in clustered configurations to force load balancing between a runnin...
Post a Comment
Read more