Upgrade ESXi 6.x to 6.7 via CLI – Two methods

Upgrade ESXi 6.x to 6.7 via CLI – from VMware OnLine depot

Step 0: Enable swap on local datastore – connect to your ESXi host via HTML5 host client by typing https://IP_or_FQDN/ui and going to the Manage > System > Swap > Edit Settings > Drop Down and Select your local datastore.

Note: If you don’t do that, you’ll end up with an installation error saying “Failed updating the bootloader: Execution of command /usr/lib/vmware/bootloader-installer/install-bootloader failed: non-zero code returned…. return code: 1”

Step 1: Connect to your ESXi host via host client and enable SSH (if you haven’t already done yet), then enter a maintenance mode and enable one firewall rule for web traffic (disabled by default) with this command:

esxcli network firewall ruleset set -e true -r httpClient

Step 2: Enter this command to list all available profiles. We filter only those which are relevant to our case – upgrade to ESXi 6.7

esxcli software sources profile list -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml | grep -i ESXi-6.7

You’ll see two profiles. We pick the “ESXi-6.7.0-8169922-standard” one for our situation.

Step 3: The upgrade – Execute this command which will use the profile to upgrade the ESXi 6.x host

Note: The -p stands for “profile” and the -d stands for “depot”.

And you should see the message saying that the upgrade was successful.

Reboot the host to complete the upgrade process and you are done.

Upgrade ESXi 6.x to 6.7 via CLI – via “Offline Bundle”

The offline bundle is a file which is available for paid customers only. Free ESXi users do not have an access to this download.

Step 0: The same as for the method above. You have to enable swap on the local datastore.

Step 1: After downloading the “VMware-ESXi-6.7.0-8169922-depot.zip” file, place it (upload it) to a datastore which is visible by your ESXi host. Best would be a local datastore, if this host has some. If not, it can also be a shared datastore too.

Put your host into maintenance mode, enable SSH if you haven’t done yet.

Step 2: Execute this command to upgrade your ESXi 6.x to 6.7

esxcli software profile update -p ESXi-6.7.0-8169922-standard -d /vmfs/volumes/your_datastore/VMware-ESXi-6.7.0-8169922-depot.zip

Where “your_datastore” is the name of the datastore where you have uploaded the Offline bundle file.

After checking that your upgrade was successful, reboot your host. You should see a message saying that the upgrade completed successfully.

Wrap Up:

As you can see, both methods are similar where the first one uses VMware Online depot (accessible to anyone) and the second one supports environments without an Internet access. Both methods are supported upgrade methods.

You can use those upgrade possibilities if you do not use VMware vCenter server. However If you have vCenter server license, it’s pretty much easier to use VMware Update Manager (VUM) whcih is the tool to conduct those upgrades, especially for clustered environments.

How do I configure MAC address filtering on my DIR-850L router?

How do I configure MAC address filtering on my router?
Note: MAC Address filtering is used to control network access based on the MAC Address of the network adapter. This feature can be configured to ALLOW or DENY network/Internet access.
________________________________________
Step 1: Open your Internet browser and enter http://dlinkrouter, http://dlinkrouter.local, or http://192.168.0.1 into the address bar.

Step 2: Enter your login information in the fields provided. The default username is Admin. Enter your administrator password. If you have not changed the default password, leave this field blank. Clink Login.

Step 3: Click on Advanced tab and then Network Filter on the left-hand side.

Step 4: From the Configure MAC Filtering drop down, select your method of MAC filtering.
•    Turn MAC Filtering OFF
•    MAC Filtering ON and ALLOW computers listed to access the
network.
•    MAC Filtering ON and DENY computers listed to access the network
Step 5: Select your computer from the List or enter the MAC addresses manually.
Click Save Settings

How To Upgrade ESXi 6.x to 6.7 via ISO

This is to upgrade VMware ESXi 6.x to 6.7 via ISO image. There are several ways of upgrading standalone ESXi hosts, and via the ISO image it’s just so simple that I wanted to show this for the newcomers and people who just starting with VMware technology.

VMware ESXi is one of the most popular hypervisors around. You don’t have to fear of upgrades, especially when you know that you can revert back an upgrade. Yes, in case you having problems after upgrading, you can simply hold SHIFT + R and chose to roll back.

Here is a screenshot from the UI. 

Upgrade ESXi 6.x to 6.7 via ISO – The steps

Step 1 – Download the ESXi 6.7 Installation ISO from VMware and use clean CD-ROM to burn the ISO to the media and prepare ESXi 6.7 CD-ROM.

Note: If you have a server which supports remote connections such as ILO, iDrak or iPMI, you don’t have to use physical CD-ROM. You can attach the ISO image directly and boot up your host.

Step 2 – Go to the BIOS of your ESXi host and set the boot sequence to boot from CD-ROM first. Like this, the server will boot from the CD-ROM. Boot up your server, follow the installer’s instructions.

NOTE: You’ll need to know the root password of the previous ESXi installation. If not, you won’t be able to upgrade. I mean, it’s quite logical, but we had some questions like “what if we do not have root password”…..

The installer continues, and then, when you’ll be at the page where the installer founds an existing VMFS partition, leave the first option selected. It’s the “Upgrade ESXi, preserve VMFS datastore”. This is the option we need.

Hit OK and let the installer to upgrade your host.

After, you’ll get a prompt to remove the ISO and reboot to finish the upgrade process. The ESXi will now boot and the new ESXi 6.7 will get loaded.

The whole process is very straightforward and simple to use.

For installation where you have managed ESXi hosts by a vCenter server, you might want to use other methods of an upgrade, but we will detail them in another post. This method is useful when you have a single or just a few standalone ESXi hosts to upgrade. Not dozens or hundreds.

After the upgrade finished you can test the new HTML5 host client which brought significant improvements for VM and host management. I’m sure you know, but folks coming from earlier versions of ESXi and still perhaps using the old vSphere Windows client, might not know.

Simply connect to your host via IP address or FQDN, like this:

https://IP_or_FQDN/ui

To get to the login screen and the version of the ESXi.

Wrap Up:

This method is simple and effective for upgrading standalone ESXi hosts. You still keep a possibility to revert back in case something goes wrong. For standalone ESXi, you obviously have to shut down your running VMs before an upgrade.

Note that at the moment, VMware does not supports upgrades from ESXi 6.5U2 so if you’re on ESXi 6.5 do not install the U2 which has been released recently, but rather wait for an upcoming patch.

Determining detailed build number information for VMware hosts (1012514)

Details

In some cases, after patches have been installed on an ESX host, different build numbers are reported for different components. This article provides details of the build information for 4.0.x and newer hosts.

For information on ESX 3.0x or ESX 3.5.x hosts, see Determining detailed build number information for VMware ESX 3.0.x and 3.5.x hosts (1001179).

Solution

VMware ESX hosts are patched according to a model where each patch bundle only updates a few components of the ESX installation at a time. Not all components of the installation are upgraded during each patch installation. When a patch is applied, the build number of the updated components changes. As a result, the ESX installation can have different components at different build numbers, depending upon which patch bundles have been applied.

You can view the build number for different components of upgraded versions of ESX 4.0.x. This article provides instructions on how to determine the build number of:

• The system level
• The build number
• The patches applied to the host
• The currently installed RPMs
• The host agent component
• RPMs and VIBs in patches before installation
• RPMs and VIBs in patches after installation
• RPM in a specific bulletin

For more information on how to determine the build number of other VMware products, see Determining VMware Software Version and Build Number (392).

To determine the system level of a host:

Note: This displays the build number of the latest update applied (for example, ESX 4.0.0 Update 1):

1. Log in to the ESX service console or locally to the ESXi host.
2. In the command prompt, run the command:
   
   #vmware -l
   
   You see an output similar to:
   
   #VMware ESX 4.0.0 Update 1
   
   The system level base installation of the ESX host will be displayed in the query output. This is the system level with no updates applied.

To determine the build number of a host:

Note: This displays the build number of ESX. The build number for ESX changes for any GA (general availability) or update release (like ESX 4.0 Update 1). Because patch releases do not deliver a vmware-esx-vmware-release rpm, they do not affect the build number displayed by vmware -v.

1. Log in to the ESX service console or locally to the ESXi host.
2. In the command prompt, run the command:
   
   #vmware -v
   
   You see an output similar to:
   
   #VMware ESX 4.0.0 build-208167

To determine the patches or updates applied on the ESX host:

1. Log in to the ESX service console.
2. In the command prompt, run the command:
   
   #esxupdate query
   Lines in the output indicate the names and of patches that might have been applied after the original installation. Typical output is similar to:
   
   ----Bulletin ID---- -----Installed----- -------------Summary-------------
   ESX400-200906401-BG 2009-07-08T18:02:49 Updates VMX
   ESX400-200906412-BG 2009-07-08T18:02:49 Updates esxupdate
   ESX400-200906404-BG 2009-07-08T18:02:49 Updates CIM

To view the build numbers of all RPMs currently installed on the ESX host:

1. Log in to the ESX service console.
2. In the command prompt, type:
   
   rpm -qa | grep -i vmware
   This method reports build numbers for all ESX components (RPMs) including VMX, host agent, VMkernel, drivers, and so on.

To view the current build number of the host agent component:

1. Log in to the ESX host using the VI Client.
2. Choose Help > About Vmware vSphere
   
   Note: In ESX 4.0, the packages are called VIBs (vSphere Installation Bundle). The VIB name contains details about the RPMs, including the versions.

To view the build numbers of RPMs and VIB details contained in a patch bundle before it is installed:

1. Download the patch bundle zip files as described in the patch bundle installation instructions.
2. Before installing the patch, change to the directory that you use as your esxupdate repository. For example, if your repository is located at /var/updates, type:
   
   #cd /var/updates
3. In the command prompt, type:
   
   #esxupdate --bundle patchbundlename.zip info
   
   Where patchbundlename represents the name of patch bundle.

To view the build numbers of RPMs and VIB details contained in a patch bundle after it is installed:

1. Log in to the ESX Server service console.
2. In the command prompt, type:
   
   # esxupdate info
   
   This command lists all the VIBs.

To view the build numbers of RPMs in a specific bulletin contained in a patch bundle after it is installed:

1. Log in to the ESX Server service console.
   
   In the command prompt, type:
   
   # esxupdate info -b bulletinname
   
   Where bulletinname represents the name of the bulletin you are reviewing, such as ESX400-200906413-BG.

Sample output for the command: esxupdate info -b bulletinname:
Id	- ESX400-200906413-BG
Releasedate	- 2009-07-09T00:00:00-08:00
Vendor	- VMware, Inc.
Summary	- Updates vmkernel iSCSI Driver
Severity	- critical
Category	- critical
Installdate	- 2009-07-02T16:25:56.709691+05:30
Description	- This patch fixes an issue where iSCSI targets might disappear during controller fault or failover of an EqualLogic array. Currently, this issue has only been observed on EQL hardware. However it might not be specific to EQL arrays. Please see http://kb.vmware.com/kb/1012232 for more details
Kburl	-http://kb.vmware.com/kb/1012232
List of constituent VIBs:	-rpm_vmware-esx-iscsi_4.0.0-0.5.175625@i386 rpm_vmware-hostd-esx_4.0.0-0.5.175625@i386

Another method of finding out the information above is using vSphere PowerCLI.

To determine the system level and build number of an ESX 4.0 host using PowerCLI:

1. Open the PowerCLI command prompt.
2. Connect to the ESX or ESXi host which reported the warning using the command:
   
   Connect-VIServer -Server ESXHostnameOrIPAddress
   
   Note: Authenticate using an administrative user, such as root.
   
3. Run this command:
   
   get-view -ViewType HostSystem -Property Name, Config.Product | select Name,{$_.Config.Product.FullName},{$_.Config.Product.Build} | ft -auto
   

To determine the patches or updates applied on the host, run this command:

Get-VMHost hostname | Get-VMHostPatch | Select Id,InstallDate,Description | ft -auto

For more information about esxupdate commands in vCLI, see the vSphere Command-Line Interface Reference.

To determine the patches or updates applied on the ESXi host:

1. Log in locally to the ESXi host.
2. In the command prompt, run the command:
   
   #esxcli software vib list

Note: For more information, see Correlating vCenter Server and ESXi/ESX host build numbers to update levels (1014508).

How to Install latest ESXi VMware Patch

If you have just installed the latest VMware vSphere 6 for example and want to patch, but you don’t know how? This guide is especially useful if your ESXi host is not connected to the internet. Many folks are waiting for VMware to “polish” the 6.0 release the latest patches which don’t break things, but that’s not always the case.

The latest patch is cumulative. Those of you who stepped in and runs vSphere 6.7, you might want to install the latest ESXi VMware patch. By having the latest patch, you’re not only safe, but you might also be safe from bugs, which appears after major releases.

So in today’s post, we look at the patching process. Where to download the latest patches and how to apply them to the host. We will focus on simple CLI method today for environments with single ESXi host. This can be the case for branch office or a test environment or simply a site without the resources to purchase a license package that includes vCenter.

Step 1: The patch download portal first (you need VMware login – create a free account if you haven’t done yet).

Select the product you want to download patches (in our case ESXi 6.7)

Select the patch you want to download. (they are cumulative, download only the latest one).

Step 2: Download the ZIP file and upload it to a datastore (via VMware vSphere client or via WinSCP for example) that is reachable for the host you want to patch (it can be local or shared datastore) > Bring the host into the maintenance mode > Connect with SSH (via Putty for example or through Firefox and FireSSH) to your ESXi host.

To enable SSH go and select your host > configuration > security profile > services > properties > SSH.

Then connect via SSH and run this command:

esxcli software vib install -d /vmfs/volumes/datastore1/patch-directory/ESXi670-201901001.zip

So in my case, it was:

esxcli software vib install -d/vmfs/volumes/465/ESXi670-201901001.zip

Reboot the host and leave the maintenance mode.

You’re done. In case you have a vSphere cluster in place you can leverage VMware Update Manager (VUM) which can orchestrate the patching across your cluster where it goes and puts the host in maintenance mode and evacuates VMs via vMotion automatically each time a host within cluster needs to be patched. So you just attach a baseline which includes the latest patches > scans the cluster > remediate….

You will certainly not patch as I showed in this guide today. But today’s post is certainly useful for isolated, lab environments, or environments where VUM isn’t installed.

Unlicensed Product and activation errors in Office

If Office activation fails, you'll see Unlicensed Product or Non-commercial use / Unlicensed Product in the title bar of your Office apps, and most features of Office are disabled. To restore all features of Office, you'll need to fix the problem that's causing activation to fail.

Step 1: Sign in to Office with the right account
If Office asks you to sign in, enter the account you used to buy Office. You'll see "We couldn't find any Office products" if you use the wrong address.
Try this: Sign in to Office

Step 2: Check for multiple copies of Office
You may not realize you have more than one copy installed. Having two installs can cause activation conflicts.
Try this: Check for multiple copies of Office

Step 3: Check your subscription status
If your subscription has expired, you'll see "We couldn't find any Office products." Renew your subscription to use Office 365.
Try this: Check your subscription status

Step 4: Troubleshoot activation
If Office still won't activate, choose your Office version for additional troubleshooting help.
Office 365
Office 2019 and Office 2016
Office 2013

Step 1: Sign in with the right account

Please try signing in using all your personal email addresses in case you bought Office using a different email address. If you're at work or school, you may need to log in using your work or school account instead of your personal email account.

To check if your Microsoft account is associated with Office, sign in to Services & subscriptions. Your Office product or Office 365 subscription should be listed there. If it's not, your email address won't work for signing in to Office.

Step 2: Check for multiple copies of Office

Activation can fail if you have multiple copies of Office installed. Let's uninstall any versions of Office you aren't using before we continue to troubleshoot.

1. Open Control Panel using the steps below for your operating system:
   • Windows 10 On the Windows 10 task bar, type Control Panel in the Type here to search box, select Control Panel in the search results, and then select Programs and Features.
   • Windows 8.1 or 8 Right-click the Start button (lower-left corner), select Control Panel, and then select Programs and Features.
   • Windows 7 Click Start > Control Panel > Uninstall a program.
2. In the Search Programs and Features box (upper-right corner) of Programs and Features, search for the word office.
   You might see multiple versions installed, like this:
    
3.  If more than one version appears, right-click the version you aren't using and select Uninstall.
   If only one version is listed, you can go to Step 3: Check your Office 365 subscription status.
4. When the uninstall is finished, restart your computer.
5. Open an Office app and sign in, if prompted.
6. If Office still won't activate, try running an online repair as described in Repair an Office application to fix up the remaining install of Office. If you still can't activate, proceed to the next step.

Step 3: Check your Office 365 subscription status

If you have an Office 365 for home subscription, let's make sure it's still active and renew your subscription, if necessary.

If you don't have Office 365, you can skip to Step 4: Troubleshoot Office activation.

1. Close all Office apps.
2. Go to your Services & subscriptions page.
3. If prompted, choose Sign in and enter the Microsoft account email and password associated with your Office 365 subscription.
4. Review the details under the Subscriptions heading or Cancelled subscriptions heading.
   
5. If your subscription has expired, you can renew it by following the steps in Renew Office 365 for home.
6. After you renew your subscription, you can restart your Office apps as needed. If Office still won't activate, continue to the next step

Step 4: Troubleshoot Office activation

Select your version of Office for troubleshooting steps:

Office 365

Office 2019 and Office 2016

Office 2013

Office 365: Use the Support and Recovery Assistant for Office 365

The Support and Recovery Assistant app runs on Windows PCs and can help you identify and fix activation issues with Office 365.

1. Select the Download button below.
   
2. Select your browser from the drop-down list to see how to save and then start the Support and Recovery Assistant for Office 365.
   
   

   Select your browser

   

   
   

   • Select your browser
   • Edge
   • Internet Explorer
   • Chrome
   • Firefox
   1. At the bottom of the browser window, select Save.
   2. In the next box that indicates SetupProd_Act.exe is finished downloading, select Run.

   1. At the bottom of the browser window, select Open to open the SetupProd_Act.exe file.
      If the file doesn’t open automatically, choose Save > Open Folder, and then double-click the file (it should start with "SetupProd_Act.exe").

   1. In the lower-lower left corner select the SetupProd_Act.exe file and from the drop down, select Show in folder.
      Double-click the download, SetupProd_Act.exe.

   1. Select Save File, and then OK.
      In the upper-right browser window, select Show all downloads. In the Library, select Downloads > SetupProd_Act.exe, and then select the folder icon. Double-click SetupProd_Act.exe.
3. The Application Install dialog box opens. Select Install to start the installation.
4. The Microsoft Support and Recovery Assistant for Office 365 opens in a new window. Select I agree to accept the Microsoft Services Agreement.
5. Select Yes to allow the app to make changes to your device.
6. Follow the prompts to troubleshoot your Office activation issue.

If Office still won't activate after you run the Support and Recovery Assistant, you can Fix Unlicensed Product errors yourself.

Office 2019 and Office 2016: Use the Activation Troubleshooter (non-subscription Office products)

The Activation Troubleshooter runs on Windows PCs and can fix activation errors for Office Home & Student, Office Home & Business, Office Professional, and individual Office apps, like Visio, Project, Word, and Outlook.

1. Select the Download button below.
   
2. Select your browser from the drop-down list to see how to save and then launch the troubleshooter.
   
   

   Select your browser

   

   
   

   • Select your browser
   • Edge
   • Internet Explorer
   • Chrome
   • Firefox
   1. At the bottom of the browser window, select Save.
   2. In the next box that indicates officeact.diagcab is finished downloading, select Open.
   3. The Activation Troubleshooter launches. Select Next and follow the prompts.

   1. At the bottom of the browser window, select Open to open the officeact.diagcab file.
      If the file doesn’t open automatically, choose Save > Open Folder, and then double-click the file (it should start with "officeact.diagcab") to run the easy fix tool.
   2. The Activation Troubleshooter launches. Select Next and follow the prompts.

   1. In the lower-lower left corner select the officeact.diagcab file and from the drop down, select Show in folder.
      Double-click the download, officeact.diagcab to run the easy fix tool.
   2. The Activation Troubleshooter launches. Select Next and follow the prompts.

   1. Select Save File, and then OK.
      In the upper-right browser window, select Show all downloads. In the Library, select Downloads > officeact.diagcab, and then select the folder icon. Double-click the officeact.diagcab.
   2. The Activation Troubleshooter launches. Select Next and follow the prompts.

If Office still won't activate after you run the Activation Troubleshooter, you can Fix Unlicensed Product errors yourself.

Fix Unlicensed Product errors yourself

If you've tried the earlier troubleshooting steps and Office is still unlicensed, you can troubleshoot activation failures yourself.

Try these first

Check your computer's date, time, and time zone
Run Office as administrator
Update Office
Repair Office licensing (Office 2013 only)

Check connectivity

Check your firewall
Check your antivirus software
Check your proxy settings

Check your computer's date, time, and time zone

If these settings aren't correct, Office activation might fail. Follow the steps below for your operating system.

Windows 10

1. Close all Office apps.
2. In the bottom right-hand corner of your screen, select the date or time.
3. Select Date and time settings.
4. Select Set time automatically and, if shown, Set time zone automatically. If you don't have the option to set the time zone automatically, make sure your local time zone is shown in Time zone.
5. Restart any Office app.

Windows 8 or Windows 8.1

1. Close all Office apps.
2. In the bottom right-hand corner of your screen, select the date or time.
3. Select Change date and time settings.
4. If the date or time is wrong, select Change date and time and correct the date and time settings.
5. If the time zone is wrong, select Change time zone and select your local time zone.
6. Restart any Office app.

Windows 7

1. Close all Office apps.
2. In the bottom right-hand corner of your screen, select the date or time.
3. Select Change date and time settings.
4. If the date or time is wrong, select Change date and time and correct the date and time settings.
5. If the time zone is wrong, select Change time zone and select your local time zone.
6. Restart any Office app.

Tip: In Windows 7, you can synchronize your computer clock with an Internet time server to keep the computer clock up to date. To do this, select the date or time in the bottom right-hand corner of your screen, and then select Change date and time settings. Select the Internet Time tab, select Change settings, select Synchronize with an Internet time server, and then select Update now.

Run Office as administrator

Running Office as administrator helps fix permission issues that might cause Office activation to fail. Follow the steps below for your operating system.

Windows 10

1. Close all Office apps.
2. Press the Start button in the lower-left corner of your screen.
3. Type an application name, like Word. The Word program icon appears in the search results.
4. Right-click the Word icon, and select Run as administrator.
5. Select Yes to allow Office to run as administrator.

Windows 8.1

1. Close all Office apps.
2. In Windows 8.1, right-click the Start button in the lower-left corner of your screen, and then select Search.
3. Type an application name, like Word. The Word program icon appears in the search results.
4. Right-click the Word icon, and select Run as administrator.
5. Select Yes to allow Office to run as administrator.

Windows 8

1. Close all Office apps.
2. In Windows 8, move your mouse to the upper-right corner of your screen to open the charms bar, and then select the Search icon.
3. Type an application name, like Word. The Word program icon appears in the search results.
4. Right-click the Word icon, and select Run as administrator.
5. Select Yes to allow Office to run as administrator.

Windows 7

1. Close all Office apps.
2. Press the Start button in the lower-left corner of your screen.
3. In the Search programs and files box, type an application name, like Word. The Word program icon appears in the search results.
4. Right-click the Excel icon, and select Run as administrator.
5. If prompted, select Yes to allow Office to run as administrator.

Update Office

The latest Office updates might contain fixes to activation issues. To learn how to update Office, see Install Office updates.

Repair Office licensing (applies only to Office 2013)

If you’ve tried all of the other solutions but you’re still getting prompted to activate Office 2013, uninstall your product key and then sign in to activate Office.

1. Select this easy fix to uninstall your product key in Office 2013.
   
2. At the bottom of your browser, select Open.
   
3. After the easy fix tool is done, open any Office application, like Word or Excel.
4. When you’re prompted, sign in with the email and password that are associated with Office.

Check your firewall

If you're using a firewall from another manufacturer, visit the manufacturer's website for information about how to temporarily disable the firewall. For Windows Firewall, please see below.

Windows 10

• Please go to Turn Windows Firewall on or off

Windows 8.1 and 7

• Please scroll to Turn Windows Firewall on or off in Protect my PC from viruses

Check your antivirus software

For information about how to turn off your antivirus software, check your antivirus manufacturer's website. Uninstalling your antivirus software may also help. Don't forget to reinstall it after Office is finished installing and if you turned it off, be sure to turn it on again.

If you're not sure which antivirus software you have, use the following instructions to get to Control Panel to find the name of your antivirus software.

Tip: Windows 10 comes with default antivirus software, Windows Defender. If you determine that you're using it, select the Start button > Settings > Update & Security, and then select Windows Defender on the left. Slide the button to Off. Remember to turn it On again.

Select your operating system



• Select your operating system
• Windows 10
• Windows 8.1
• Windows 7

1. On the Start menu, enter Control Panel in the search box and select Control Panel from the results.
2. Do one of the following:
   • In Category view, select System and Security > Security and Maintenance, and then select the down arrow next to Security.
   • In Large icons or Small icons view, select Security and Maintenance, and then select the down arrow next to Security.

If Windows can detect your antivirus software, it's listed under Virus protection.

1. Go to the Control Panel by right-clicking the Start button (lower-left corner), and choosing Control Panel.
   
2. Do one of the following:
   • In Category view, select System and Security > Action Center, and then select the down arrow next to Security.
   • In Large icons or Small icons view, select Action Center, and then select the down arrow next to Security.

If Windows can detect your antivirus software, it's listed under Virus protection.

1. Go to Control Panel by choosing the Start button (lower-left corner), and choosing Control Panel.
2. Do one of the following:
   • In Category view, select System and Security > Action Center, and then select the down arrow next to Security.
   • In Large icons or Small icons view, select Action Center, and then select the down arrow next to Security.

If Windows can detect your antivirus software, it's listed under Virus protection.

Check your proxy settings

If you use your device both at home and at work, try turning off the proxy settings in Microsoft Edge or Internet Explorer before you install Office. If you’re using a different browser, check their help to find out how to turn off proxy settings.

Microsoft Edge

1. Click the Start button (lower-left corner), and choose Settings.
2. Select Network & Internet, go to the bottom of the selections on the left side, and click Proxy.
3. In Automatic proxy setup, automatically detect settings or use setup script, by sliding to On or Off.
4. In Manual proxy setup, you can choose to use a proxy server. Generally, it will be off and if you slide it to On, be sure to select Save. And if it was off by default before you turned it on, be sure to slide back to Off when you've finished using it.

Internet Explorer 7, 8, 9, 10, or 11

1. In Internet Explorer, click Tools (upper-right corner) > Internet options.
2. Click the Connections tab, and then click the LAN settings button.
3. Under Proxy server, clear the option "Use a proxy server for your LAN (These settings will not apply to dial-up or VPN connections)."
4. Click Apply and OK to save changes. Restart your computer.

Note: There might be more proxy settings that you need to bypass. If this doesn't work, and you’re installing Office from work or school, check with your IT department for more information. For IT administrators, please see Office 365 URLs and IP address ranges.