IT NOTEs: vista

Showing posts with label vista. Show all posts

Wednesday, February 23, 2011

Vista/Win7 - User Profile Error - Logged on with a Temporary Profile

Article from: http://www.vistax64.com/tutorials/135858-user-profile-error-logged-temporary-profile.html

EXAMPLE: Error Message in Windows 7

STEP ONE

Log On to the Computer as an Administrator

Warning

You must be logged on to an administrator account using either step 1 or 2 below before you can move on to do the STEP TWO section below.

1. To Log on to another Administrator account
NOTE: If you do not have another Administrator account, then proceed to step 2.

A) Go to the STEP TWO section below.

OR

2. To Boot into Safe Mode for the built-in Administrator account
NOTE: You may not need to enable the built-in Administrator account. If this was the only normal administrator account you had, then Safe Mode should automatically boot into the built-in Administrator account.

Tip

If you cannot boot into Windows and do not have a Windows installation DVD, then you can create and use the boot disc below to boot into Safe Mode with instead.

Windows 7: (Option Two at link)
How to Create a Windows 7 System Repair Disc

Vista: (Option One at link)
How to Create a Vista Recovery Disc

A) Boot into Safe Mode (in Vista) or Safe Mode (in Windows 7).

B) If Safe Mode did not boot into the built-in Administrator
account, then enable the built-in Administrator account. If it did , then go to step 2C.

C) Log off in Safe Mode, and then log on to the built-in Administrator account to logon with that account in Safe Mode.

D) Go to the STEP TWO section below.

STEP TWO

Delete the User Account Profle SID Key

1. Delete the User account profile that this error is for, but do not delete the C:\User\(user-name) folder at step 4 in that link.

Warning

You should backup anything you do not want to lose in this user account's user folders first. (See note in step 11) They will be located in the C:\Users\(username) folder.

2. Open the Start menu.

3. In the white line (Start Search) area, type regedit and press Enter.

4. If prompted by UAC, then click on Continue (Vista) or Yes (Windows 7).

5. In regedit, go to: (See screenshot below step 7)

Code:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

6. In the left pane, click on one of the S-1-5..... folders (SID key) with the long number in it. (See screenshot below step 7)
NOTE: It should have .bak at the end of it.

A) In the right pane, look at the ProfileImagePath to see if this is the same user account that you deleted in step 1 above.

B) Repeat step 6 until you find the one that you deleted in step 1 above.

7. To Backup the Registry SID Key
WARNING: You should backup this SID key to be safe in case you delete the wrong one in step 8 below.

A) Right click on the SID key, and click on Export.

B) Type in a name and save the REG file to a safe location.
NOTE: This is your backup. To Restore the Backup, right click on the REG backup file and click on Merge.

C) Continue on to step 8.

8. Right click on the SID key, from step 6 with bak at the end, and click on Delete. (See screenshot above)

9. Click on Yes to confirm deletion. (See screenshot below)

10. Close regedit.

11. Log off and log on.
NOTE: After you logon to the computer, the profile folder you are having problems with is re-created. If not, then try a System Restore using a restore point dated before you got this error. If this still dows not help, then you will need to create a new account and restore the user folder files afterwards from the warning in step 1.

Saturday, April 4, 2009

How to change entries in VISTA boot loader !!!

http://www.flexbeta.net/forums/lofiversion/index.php/t8373.html

=====================
Modify your VISTA Boot Menu
=====================

Do you also have several cryptical entries in your personal new VISTA bootloader?

Does it look like:

Legacy (pre-Longhorn) Microsoft Windows Operating System
Microsoft Windows
Microsoft Windows
Microsoft Windows
Microsoft Windows
....

Don't know which Windows is which entry?

Then you need this new guide with my experiences!

You will get a "new" boot menu! For example:

Legacy (pre-VISTA) XP, 2000, 2003, WIN98x
VISTA 5259 TAP
VISTA 5231 IDX
WINDOWS SERVER 2003

======
Theory
======

Till VISTA build 5231 we have had the new VISTA LOADER and for XP, 2000, 2003
and Win 98 the all known NTLDR called NT Loader or NT Bootloader and the mirror
of that is BOOT.INI...

With VISTA 5259 we have a new hierarchy:

First loader: VISTA loader called bootmgr, a "BOOTMANAGER"
Second Loader: NTLDR (XP,2003,98...)

VISTA looks in its "DATA STORE", were the new entries will be hold.
In the beta state of VISTA we have only two programs, which can help us:

MSCONFIG (which does not see the legacy OS)
BCDEDIT.EXE

==========
BCDEDIT.EXE
==========

Please press START and RUN (have you activate "RUN"? >Go to ADMINISTRATOR, right-click Taskbar, Properties, Start Menu, Start Menu Customize, check Run command, OK) and type in: command and press OK.

Yes, it looks like MS-DOS! It's name is Windows DOS...

Then you must type in: bcedit
and the nice program starts and shows for example this:

Microsoft® Windows DOS
©Copyright Microsoft Corp 1990-2001.

D:\USERS\ADMINI~1>bcdedit

Windows Boot Manager
--------------------
Identifier: {bootmgr}
Type: 10100002
Device: partition=C:
Description: Windows Boot Manager
Locale: ENG-US
Inherit options: {emssettings}
{dbgsettings}
Default: {871d699a-68d1-11da-9f30-eb66f9279051}
Display order: {legacy}
{871d699a-68d1-11da-9f30-eb66f9279051}
{d3e15d7c-66fb-11da-83c4-f23116dca051}
{77e994d8-64b9-11da-afd6-cd1e42667751}
{748c9ce4-6497-11da-b587-ba41a6a3f856}
{6bde53aa-630a-11da-b591-bb4bd04c9f19}
{d9b222a6-5f5b-11da-8e9c-87c5457d571e}
{eafe9a2c-558c-11da-86bb-9237c2e1a919}
{3ffee100-4b31-11da-b300-e812ef50ad19}
{eda3906c-438e-11da-b934-f4ecbe0a3419}
{4f964faa-3d7a-11da-bb88-b7df6f4d4219}
Timeout: 3

Windows Legacy OS Loader
------------------------
Identifier: {legacy}
Type: 10300006
Device: partition=C:
Path: \ntldr
Description: Legacy (pre-Longhorn) Microsoft Windows Operating System

Windows Boot Loader
-------------------
Identifier: {871d699a-68d1-11da-9f30-eb66f9279051}
Type: 10200003
Device: partition=H:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: en-US
Inherit options: {emssettings}
{dbgsettings}
{5189b25c-5558-4bf2-bca4-289b11bd29e2}
Windows device: partition=H:
Windows root: \Windows
No Execute policy: OptIn

Windows Boot Loader
-------------------
Identifier: {d3e15d7c-66fb-11da-83c4-f23116dca051}
Type: 10200003
Device: partition=H:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: en-US
Inherit options: {emssettings}
{dbgsettings}
{5189b25c-5558-4bf2-bca4-289b11bd29e2}
Windows device: partition=H:
Windows root: \Windows
No Execute policy: OptIn

Windows Boot Loader
-------------------
Identifier: {77e994d8-64b9-11da-afd6-cd1e42667751}
Type: 10200003
Device: partition=H:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: en-US
Inherit options: {emssettings}
{dbgsettings}
{5189b25c-5558-4bf2-bca4-289b11bd29e2}
Windows device: partition=H:
Windows root: \Windows
No Execute policy: OptIn

Windows Boot Loader
-------------------
Identifier: {748c9ce4-6497-11da-b587-ba41a6a3f856}
Type: 10200003
Device: partition=D:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: ENG-US
Inherit options: {emssettings}
{dbgsettings}
Windows device: partition=D:
Windows root: \Windows
No Execute policy: OptIn
Detect hal: Yes

Windows Boot Loader
-------------------
Identifier: {6bde53aa-630a-11da-b591-bb4bd04c9f19}
Type: 10200003
Device: partition=J:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: ENG-US
Inherit options: {emssettings}
{dbgsettings}
Windows device: partition=J:
Windows root: \Windows
No Execute policy: OptIn
Detect hal: Yes

Windows Boot Loader
-------------------
Identifier: {d9b222a6-5f5b-11da-8e9c-87c5457d571e}
Type: 10200003
Device: partition=J:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: ENG-US
Inherit options: {emssettings}
{dbgsettings}
Windows device: partition=J:
Windows root: \Windows
No Execute policy: OptIn
Detect hal: Yes

Windows Boot Loader
-------------------
Identifier: {eafe9a2c-558c-11da-86bb-9237c2e1a919}
Type: 10200003
Device: partition=J:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: ENG-US
Inherit options: {emssettings}
{dbgsettings}
Windows device: partition=J:
Windows root: \Windows
No Execute policy: OptIn
Detect hal: Yes

Windows Boot Loader
-------------------
Identifier: {3ffee100-4b31-11da-b300-e812ef50ad19}
Type: 10200003
Device: partition=J:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: ENG-US
Inherit options: {emssettings}
{dbgsettings}
Windows device: partition=J:
Windows root: \Windows
No Execute policy: OptIn
Detect hal: Yes

Windows Boot Loader
-------------------
Identifier: {eda3906c-438e-11da-b934-f4ecbe0a3419}
Type: 10200003
Device: partition=J:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: ENG-US
Inherit options: {emssettings}
{dbgsettings}
Windows device: partition=J:
Windows root: \Windows
No Execute policy: OptIn
Detect hal: Yes

Windows Boot Loader
-------------------
Identifier: {4f964faa-3d7a-11da-bb88-b7df6f4d4219}
Type: 10200003
Device: partition=J:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: ENG-US
Inherit options: {emssettings}
{dbgsettings}
Windows device: partition=J:
Windows root: \Windows
No Execute policy: OptIn
Detect hal: Yes

D:\USERS\ADMINI~1>

Sorry - a long one, but you will see, I have several entries of the same kind.
Partition H:\ three times and J:\ even more...

=========
Backup first!
=========

First of all, we need a backup/copy of our boot entries!

Step 1: Change to ADMINISTRATOR

Step 2: Type in: bcdedit -?

This will show us the HELP MENU of bcdedit.exe:

H:\USERS\ADMINI~1>bcdedit -?

BCDEDIT - Boot Configuration Data Store Editor

The Bcdedit.exe command-line tool modifies the boot configuration data store.
The boot configuration data store contains boot configuration parameters and
controls how the operating system is booted. These parameters were previously
in the Boot.ini file (in BIOS-based operating systems) or in the nonvolatile
RAM entries (in Extensible Firmware Interface-based operating systems). You can
use Bcdedit.exe to add, delete, edit, and append entries in the boot
configuration data store.

For detailed command and option information, type bdedit.exe /? . For
example, type "bcdedit.exe /? /createstore" (without quotes).

For command and option information, please run "bcdedit /? " where
is one of the help topics listed below.

/bootdebug Enables or disables boot debugging for a boot application.

/bootems Enables or disables Emergency Management Services for a boot
application.

/bootsequence Sets the one-time boot sequence for the boot manager.

/copy Makes copies of entries in the store.

/create Creates new entries in the store.

/createstore Creates a new and empty boot configuration data store.

/dbgsettings Sets the global debugger parameters.

/debug Enables or disables kernel debugging for an operating system
entry.

/default Sets the default entry that the boot manager will use.

/delete Deletes entries from the store.

/deletevalue Deletes entry options from the store.

/displayorder Sets the order in which the boot manager displays the multiboot
menu.

/ems Enables or disables Emergency Management Services for an
operating system entry.

/emssettings Sets the global Emergency Management Services parameters.

/enum Lists entries in the store.

/export Exports then contents of the system store to a file. This file
can be used later to restore the state of the system store.

formats Displays the formats of the data required by the /set command.

id Displays the identifier parameter options that can be used
in several Bcdedit commands such as /create and /copy.

/import Restores the state of the system store using a backup file
created with the /export command.

/set Sets entry option values in the store.

/store Specifies the boot configuration data store to use.

/timeout Sets the boot manager time-out value.

/types Displays the data types required by the /set and /deletevalue
commands.

/v Displays all entry identifiers in full, rather than using
shorthand notation for the well-known identifiers.

H:\USERS\ADMINI~1>

Step 3: Type in: bcdedit -? export

You will get:

H:\USERS\ADMINI~1>bcdedit -? export

bcdedit /export

This command exports the contents of the system store into a file. This file
can be used later to restore the state of the system store. This command is
only valid for the system store.

The filename to be used as the desination for the export.
If the filename contains spaces, it must be enclosed in
double quotes (").

Example:

The following example will export the system store to the specified file:

bcdedit /export "C:\Data\BCD Backup"

H:\USERS\ADMINI~1>

Step 4: Please make a new folder: C:\DATA

Step 5: Type in: bcdedit /export "C:\Data\BCD Backup"

You have now a BACKUP of bootmgr entries! With "import" you are able to restore it!!
You can afterwards also safe your new entries, no problem like:

bcdedit /export "C:\Data\BCD My New Boot Entries"

==========================
DELETE DOUBLE ENTRIES IN bootmgr
==========================

In the next step we will wipe out the double entries. (Always use your OWN identifiers!
My used one are only for explanation!!)

Step 6: Look at the double entries like: Device: partition=H:

Step 7: Type in: bcdedit -? delete

You will get:

H:\USERS\ADMINI~1>bcdedit -? delete

bcdedit -delete [-f]

This command will delete an entry from the boot configuration data store.

This specifies the identifier of the boot entry to be
deleted.

[-f] bcdedit will not delete any entries that have a well known
identifier. To force such a delete operation, specify this
flag.

Examples:

The following command will delete the specified OS entry from the store:

bcdedit -delete {cbd971bf-b7b8-4885-951a-fa03044f5d71}

The following command will delete the legacy OS loader entry from the store:

bcdedit -delete {legacy} -f

H:\USERS\ADMINI~1>bcdedit -delete {4f964faa-3d7a-11da-bb88-b7df6f4d4219}
The operation completed successfully.

H:\USERS\ADMINI~1>

Let explain with the follow examples of my bootmgr entries:

Windows Boot Loader
-------------------
Identifier: {871d699a-68d1-11da-9f30-eb66f9279051}
Type: 10200003
Device: partition=H:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: en-US
Inherit options: {emssettings}
{dbgsettings}
{5189b25c-5558-4bf2-bca4-289b11bd29e2}
Windows device: partition=H:
Windows root: \Windows
No Execute policy: OptIn

Windows Boot Loader
-------------------
Identifier: {d3e15d7c-66fb-11da-83c4-f23116dca051}
Type: 10200003
Device: partition=H:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: en-US
Inherit options: {emssettings}
{dbgsettings}
{5189b25c-5558-4bf2-bca4-289b11bd29e2}
Windows device: partition=H:
Windows root: \Windows
No Execute policy: OptIn

I want to delete the second (blue) one:
Identifier: {d3e15d7c-66fb-11da-83c4-f23116dca051}

Step 8: Type in: bcdedit -delete {d3e15d7c-66fb-11da-83c4-f23116dca051}

It is away!
All of this commands needs only the correct Identifier to scratch!
Now we can delete all other double entries in the same way.

=====================
RENAME ENTRIES in boot menu
=====================

The next step is to rename the entries.

The easiest one is the one you are in. If you have bootet VISTA 5259 TAP
you must type in:

Step 9: Type in: H:\USERS\ADMINI~1>bcdedit -set DESCRIPTION "VISTA 5259 TAP"

The operation completed successfully. Test it:

H:\USERS\ADMINI~1>bcdedit

The desription of your booted VISTA has changed from only "Microsoft Windows" to
"VISTA 5259 TAP"!

You can now boot in a other VISTA build, maybe 5231 or another. In 5231 for example there is also a BCDEDIT.EXE and you must type in the same with an other description or you are in VISTA 5259 and
you want to change the description from your "other" VISTA.

Step 10: Type in: H:\USERS\ADMINI~1>bcdedit -set {748c9ce4-6497-11da-b587-ba41a6a3f856} DESCRIPTION "VISTA 5231 IDX"

You have easily changed the description of your second VISTA, if have use the correct IDENTIFIER!

From my 6 entries about WINDOWS SERVER 2003 I have deleted 5 and renamed the last:

H:\USERS\ADMINI~1>bcdedit -set {6bde53aa-630a-11da-b591-bb4bd04c9f19} DESCRIPTION "WINDOWS SERVER 2003"

=============================
START XP/2000/20003/98x automatically
=============================

Now to the following problem:

You want to boot in your XP (2003, WIN98x) automatically?

MSCONFIG does not yet! Look in!

BCDEDIT does!

Step 11: Type in: bcdedit ? default

You will get:

H:\USERS\ADMINI~1>bcdedit -? default

This command sets the default entry that the boot manager will use when the
time-out expires.

bcdedit /default

Specifies the identifier of the boot entry to be used as the
default when the time-out expires.

Examples:

The following command sets the specified entry as the default boot manager
entry:

bcdedit /default {cbd971bf-b7b8-4885-951a-fa03044f5d71}

The following command sets the legacy Windows loader (Ntldr) as the default
entry:

bcdedit /default {legacy}

H:\USERS\ADMINI~1>

So a easy task, isn't it? You only must do Step12!

Step 12: Type in: bcdedit /default {legacy}

To look at the correct entry, look at "DEFAULT":

Microsoft® Windows DOS
©Copyright Microsoft Corp 1990-2001.

H:\USERS\ADMINI~1>bcdedit

Windows Boot Manager
--------------------
Identifier: {bootmgr}
Type: 10100002
Device: partition=C:
Description: Windows Boot Manager
Locale: ENG-US
Inherit options: {emssettings}
{dbgsettings}
Default: {legacy}
Display order: {legacy}
{current}
{d3e15d7c-66fb-11da-83c4-f23116dca051}
{77e994d8-64b9-11da-afd6-cd1e42667751}
{748c9ce4-6497-11da-b587-ba41a6a3f856}
{6bde53aa-630a-11da-b591-bb4bd04c9f19}
{d9b222a6-5f5b-11da-8e9c-87c5457d571e}
{eafe9a2c-558c-11da-86bb-9237c2e1a919}
{3ffee100-4b31-11da-b300-e812ef50ad19}
{eda3906c-438e-11da-b934-f4ecbe0a3419}
{4f964faa-3d7a-11da-bb88-b7df6f4d4219}
Timeout: 3

Yes, it worked!

========================
CHANGE {legacy} to a nicer one!
=======================

In the next and last step we will learn to change the description entry of {legacy} from:

Legacy (pre-Longhorn) Microsoft Windows Operating System

to a neater one like:

Legacy (pre-VISTA) XP, 2000, 2003 , WIN98x

Step 13: Type in: bcdedit -set {legacy} DESCRIPTION "Legacy (pre-VISTA) XP, 2000, 2003, WIN98x"

Let's have a look, how it worked:

Windows Legacy OS Loader
------------------------
Identifier: {legacy}
Type: 10300006
Device: partition=C:
Path: \ntldr
Description: Legacy (pre-VISTA) XP, 2000, 2003, WIN98x

Pefect!

With that renamed entry you will go directly in your NTLDR loader and there is working the good old
well known BOOT.INI!

Nice program, the BCDEDIT.EXE, isn't it?

Like I have read anywhere in internet MS is planning to give us a GUI for that bootmgr editing!

I hope, we will get a fast, safe, and nice VISTA 2006!

Have fun with BCDEDITing and please, don't forget to make first my described BCD Backup before
you fiddle to much and nothing worked for you after reboot.

HELP: After everey step type in: bcdedit and you will see what have worked.
Look at the "Windows Device", "Description" and "Identifiers".

Have fun!

Wednesday, January 7, 2009

Access is Denied / Encryption

http://windowshelp.microsoft.com/Windows/en-us/help/31ad4562-aee7-4fed-8316-89114dc973031033.mspx

There are two things that you can try:

•

Check the permissions of the file or folder the file is saved in. Here's how:

Right-click the file or folder, and then click Properties.

Click the Security tab.

Under Group or user names, click your name to see the permissions you have.

To open a file, you need to have read permission. For more information on permissions, see What are permissions?

•

Check to see if the file is encrypted. Here's how:

Right-click the file, and then click Properties.

Click the General tab, and then click Advanced.

If the Encrypt contents to secure data check box is selected, you need the certificate that was used to encrypt the file to open it.

You should get the certificate from the person who created the file. For more information, see Import or export certificates and private keys.

Encrypting File System (EFS) is not fully supported on Windows Vista Starter, Windows Vista Home Basic, and Windows Vista Home Premium. For those editions of Windows, if you have the encryption key or certificate, you can do the following:

•	Open Command Prompt and decrypt files by typing Cipher.exe /d at the command prompt (advanced users).
•	Modify an encrypted file.
•	Copy an encrypted file as a decrypted file to a hard disk on your computer.
•	Import EFS certificates and keys.
•	Open Command Prompt and back up EFS certificates and keys by typing Cipher.exe /r at the command prompt (advanced users).

Sunday, November 2, 2008

Start Windows in Clean Boot mode

Start Windows in Clean Boot mode

Note: You must be logged on as an administrator or a member of the Administrators group to complete this procedure.

1) Click Start.

2) Copy and paste "msconfig" (without the quotation marks) in the Start Search box, and click Enter.

3) Switch to Services tab and then Check Hide All Microsoft Services.

4) Click Disable All.

5) Switch to the Startup tab and then Click Disable all.

6) Click OK.

7) Click Restart to restart the computer and test the issue.

Wednesday, October 29, 2008

Ways to Activate your NIC

netsh int tcp set global autotuninglevel=disabled

netsh winsock reset global
netsh int ipv4 reset global
netsh int ipv6 reset global

Disable the IP Helper service:

1. Hold the Windows key and type R, enter "services.msc" (without the quotes) and press Enter
2. Scroll down to the IP Helper service, right click on it and select Properties
3. In the dropdown box that says "Automatic" or "Manual", set it to Disabled and then click on "Apply"
4. Then click on "Stop" to stop the service from running in the current session
5. Click OK to exit the dialog

Disable IPv6:

1. Hold the Windows key and type R, enter "ncpa.cpl" (without the quotes) and press Enter
2. Right click on each network connection and select "Properties"
3. Remove the checkmark from the box next to "Internet Protocol Version 6 (TCP/IPv6)
4. Click OK to exit the dialog

NOTE: You should do this for each network connection.

Disable the DHCP Broadcast Flag:

http://support.microsoft.com/default.aspx/kb/928233
1. Hold the Windows key and type R, enter regedit and press Enter.
2. Locate and then click the following registry subkey:
3. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Inter faces\{GUID}
4. In this registry path, click the (GUID) subkey to be updated.
5. If the key DhcpConnForceBroadcastFlag does not exist, use the Edit menu, point to New, and then click DWORD (32-bit) Value. In the New Value #1 box, type DhcpConnForceBroadcastFlag, and then press ENTER. If the key exists, skip this step.
6. Right-click DhcpConnForceBroadcastFlag, and then click Modify.
7. In the Value data box, type 0, and then click OK.
8. Close Registry Editor.

NOTE: You should do this for each and every GUID subkey.
NOTE2: (GUID) is a mnemonic for the individual subkeys, the actual text "GUID" does not appaer.

Logon Windows Vista as Administrator

Article from : http://maximumpcguides.com/windows-vista/logon-windows-vista-as-administrator/

Warning: Running as Administrator in Windows Vista bypasses all security (UAC) and is NOT recommended. If you decide to use the Administrator account don’t complain when you start having problems.

Enable the Administrator Account
Open the command prompt with Administrative privileges by opening the Start Menu, and typing cmd in the search box, and then press Ctrl+Shift+Enter or click the Start orb, All Programs, Accessories, right-click Command Prompt and select Run as administrator.
Type the following in the command prompt and press Enter after:

net user administrator /active:yes

Restart your computer and logon as Administrator.
Note: You might want to set a password for the administrator’s account for at least a little protection.

Disable the Administrative Account
To disable the Administrative account run the Net User command demonstrated above while logged on an account with administrative privileges but not as the Administrator account and replace yes with no.