Author: Admin

### **On iPhone:** 

1. Open **WeChat** and go to **Contacts**. 

2. Select the profile of the person you want to block. 

3. Tap the **three-dot menu** in the top right corner. 

4. Select **Profile Settings** and toggle **Block** to ON. 

### **On Android:** 

1. Open WeChat and go to Contacts. 

2. Select the profile of the person you want to block. 

3. Tap the three-dot menu in the top right corner. 

4. Select Block from the slider menu and confirm. 

Blocking someone prevents them from messaging you or seeing your Moments, but they won’t be notified that they’ve been blocked. 

That error can be frustrating, but there are a few things you can try to fix it:

1. Ensure you log in to your Office 365 account or fix login errors. You may pen Microsoft Word,, go to

2. Check Your Internet Connection. Ensure you have a stable and fast internet connection, as Copilot relies on cloud-based processing.

3. Update Microsoft Word. Go to File > Account > Update License and make sure your Word application is up to date.

4. Sign Out and Restart. Log out of your Microsoft account, close Word, and restart your computer before signing back in.

5. Try a Different Account. If you have multiple Microsoft accounts (personal vs. work), make sure you’re signed in with the correct one.

6. Reinstall Copilot. If the issue persists, uninstall and reinstall Copilot in Word.

Here are some common questions people might have about the Tesla “Key Not Detected” issue:

• Why is my Tesla showing this message?
  This warning typically appears when the car is unable to detect a valid key card, key fob, or phone key. It may be due to interference, a weak signal, or an issue with the key itself. In one case, the Tesla owner says after he opened the door, he left the phone in the garage and then drive the car without card.

• Can I still drive my Tesla if I see this message?
  Yes, you can continue driving, but once you turn off the car, you may not be able to restart it without a properly detected key.
• How do I prevent the issue?
  • Ensure your key card is placed correctly on the center console.
  • If using a phone key, make sure Bluetooth is enabled and the Tesla app is running in the background.
  • If using a key fob, check the battery and replace it if necessary.
  • Try resetting the key by holding it against the B-pillar of the driver’s side door.
• Does this happen more often with key cards than phone keys?
  Many Tesla owners report that phone keys are more reliable than key cards, as the car remains connected via Bluetooth.
• Could interference be causing the issue?
  Yes, keeping your key fob near RFID-enabled credit cards or electronic devices may cause interference, preventing proper detection.

It is essential to edit YouTube Shorts thumbnails within the YouTube application.

Navigate to YouTube Shorts.

Select the three dots icon on the Short you wish to modify.

Click Edit.

Click the Edit icon.

Select the Edit icon adjacent to the Title.

Select the thumbnail you wish to utilize.

Click the Check icon.

Click the Save button.

You’ve successfully updated the thumbnail.

Tired of your browser autofilling old addresses or saved passwords? This article provides detailed instructions for clearing Autofill data in Chrome, Firefox, Edge and Safari.  

First, for Google Chrome users: 

1. Click the **three dots** → **Settings** → **Autofill**. 

2. Choose **Passwords** to delete saved logins, or **Addresses and more** to clear old forms. 

3. Toggle off ‘Save and fill addresses’ if you want to stop autofill completely!” 

Next, for Firefox users: 

1. Open the **menu** → **Settings** → **Privacy & Security**. 

2. Scroll to **Forms & Autofill** → Click **Saved Addresses** → **Remove** what you don’t need. 

3. Under **Logins & Passwords**, delete saved entries or turn off autofill.” 

For Safari users: 

1. Open **Preferences** → **Autofill** tab. 

2. Uncheck boxes for ‘Contacts’ or ‘Other forms’ to disable autofill. 

3. Click **Edit** next to ‘User names and passwords’ to delete saved logins.” 

That’s it! Like this tip? Hit subscribe for more quick tech hacks. Comment your browser below!

For Microsoft Edge users:

To clear only Microsoft login autofill data in Edge, follow these steps:

1. Open Edge and click the three-dot menu (⋮) in the top-right corner.
2. Select Settings and go to Profiles.
3. Click Passwords and find saved Microsoft login credentials.
4. Delete the specific Microsoft login entry by clicking the trash icon next to it.
5. If autofill suggestions still appear, go to Privacy, search, and services > Clear browsing data.
6. Click Choose what to clear, select Passwords, and clear only Microsoft-related entries.

To run a preinstalled VHDX in Hyper-V, follow these steps:

1. Open Hyper-V Manager

• Search for Hyper-V Manager in the Start menu and open it.

2. Create a New Virtual Machine

• In Hyper-V Manager, right-click your host machine and select New > Virtual Machine.
• Follow the wizard to configure the VM:
  • Name: Choose a name for your VM.
  • Generation: Select Generation 1 (for legacy BIOS) or Generation 2 (for UEFI).
  • Memory: Assign RAM (e.g., 8192 MB for 8GB).
  • Networking: Select a virtual switch (or configure later).
  • Storage: Choose Use an existing virtual hard disk and browse for your VHDX file.

3. Configure VM Settings

• Right-click the newly created VM and select Settings.
• Adjust Processor settings (e.g., set 4 virtual processors).
• Modify other settings as needed.

4. Start the Virtual Machine

• Right-click the VM and select Start.
• Right-click again and select Connect to open the VM console.

5. Install Hyper-V Integration Services (if needed)

• If the guest OS lacks Hyper-V Integration Services, install it:
  • In the VM console, go to Action > Insert Integration Services Setup Disk.
  • Follow the installation prompts.

Want to set up your own Exchange Server 2019? In this quick guide, we’ll walk you through the Exchange Server 2019 installation process step by step!

Step 1: Prerequisites

Before installing Exchange 2019, ensure you have:
✅ Windows Server 2019 or later
✅ Active Directory configured
✅ .NET Framework 4.8 installed
✅ Unified Communications Managed API 4.0 Runtime
✅ Visual C++ Redistributable Packages

Step 2: Prepare Active Directory

Mount Exchange Server ISO.

Change the directory of the Mounted Exchange Server ISO to a location such as: D:

Next, prepare Active Directory for Exchange. Open PowerShell and run this command:

.\Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms_DiagnosticDataOFF

.\Setup.exe /PrepareAD /OrganizationName:”organize name” /IAcceptExchangeServerLicenseTerms_DiagnosticDataOFF

Replace “organize name” with your organization’s name, such as “chicagotech”.

.\Setup.exe /PrepareAD /OrganizationName:”chicagotech” /IAcceptExchangeServerLicenseTerms_DiagnosticDataOFF

Step 3: Install Exchange Server

Now, let’s install Exchange Server! Run Setup.exe from the ISO and follow these steps:”
✅ Select Mailbox Role
✅ Choose installation path
✅ Accept license terms
✅ Enable malware scanning

Step 4: Configure Exchange

Once installed, open the Exchange Admin Center by navigating to:”
📌 URL: https://localhost/ecp

Here, you can create mailboxes, configure send connectors, and manage users.

Resolving Exchange Error: ‘Setup.exe’ is not recognized as a cmdlet name

Some users have reported encountering the error message:

“The term ‘Setup.exe’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1

• Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms”

This issue may be due to PowerShell’s inability to recognize Setup.exe. This can occur under the following conditions:

• The command is not being run from the correct directory. To verify the Exchange Setup Path, navigate to the Exchange Server installation media (ISO or mounted folder). Change to the directory where Setup.exe is located. For example: cd D:\ExchangeSetup. Run setup.exe from this folder.
• Check for Missing Exchange Installation Files. If Setup.exe is missing, re-download the Exchange Server ISO from Microsoft’s official site. Extract the ISO and confirm Setup.exe is present.
• The .\ before Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms is missing.

Solution 1: Use .\Setup.exe

Since Setup.exe is in D:\, PowerShell requires specification of the current directory:

.\Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

Solution 2: Switch to Command Prompt

PowerShell enforces stricter execution rules, so running the command in Command Prompt (cmd) may work:

1.            Press Win + R, type cmd, and hit Enter.

2.            Run:

3.            D:\Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

Version 1

Exchange Error: The term ‘Setup.exe’ is not recognized as the name of a cmdlet

Certain users have reported encountering the following error: “The term ‘Setup.exe’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1

• Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms”

This issue appears to be due to PowerShell’s inability to recognize Setup.exe. This may happen under the following conditions:

1. The command is not being run from the correct directory. To verify the Exchange Setup Path, navigate to the Exchange Server installation media (ISO or mounted folder). Change to the directory where Setup.exe is located. For example: cd D:\ExchangeSetup. Run setup.exe from the folder.
2. Check for Missing Exchange Installation Files. If Setup.exe is missing, re-download the Exchange Server ISO from Microsoft’s official site. Extract the ISO and confirm Setup.exe is present.
3. Missing .\ before Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms is missing.

Solution 1: Use .\Setup.exe

Since Setup.exe is in D:\, PowerShell requires you to specify the current directory:

.\Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

Solution 2: Switch to Command Prompt

PowerShell enforces stricter execution rules, so running the command in Command Prompt (cmd) may work:

1.            Press Win + R, type cmd, and hit Enter.

2.            Run:

3.            D:\Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

Please ensure that these factors are correctly addressed to resolve the issue.

Exchange: The term ‘Setup.exe’ is not recognized as the name of a cmdlet

Some people report that they get this error: “The term ‘Setup.exe’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1

•              Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms”

It looks like PowerShell isn’t recognizing Setup.exe, which usually happens 1) if you’re not running the command from the correct directory; 2) if the Exchange installation media isn’t mounted properly; 3) If you miss \ before Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms.

I get this error: PS C:\Users\Administrator> Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms Setup.exe : The term ‘Setup.exe’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1

• Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

It looks like PowerShell isn’t recognizing Setup.exe, which usually happens if you’re not running the command from the correct directory or if the Exchange installation media isn’t mounted properly. Here are a few things to check:

1. Verify the Exchange Setup Path

• Navigate to the Exchange Server installation media (ISO or extracted folder).
• Open File Explorer and locate Setup.exe.
• If using an ISO, ensure it’s mounted (right-click → Mount).

2. Run the Command from the Correct Directory

• Open PowerShell as Administrator.
• Change to the directory where Setup.exe is located. For example:
• cd D:\ExchangeSetup
• .\Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
• .\Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms_DiagnosticDataOFF

If the setup is on another drive (e.g., E:), adjust the path accordingly.

3. Use the Full Path

• Instead of running Setup.exe directly, specify the full path:
• “D:\ExchangeSetup\Setup.exe” /PrepareSchema /IAcceptExchangeServerLicenseTerms

4. Check for Missing Exchange Installation Files

• If Setup.exe is missing, re-download the Exchange Server ISO from Microsoft’s official site.
• Extract the ISO and confirm Setup.exe is present.

5. Ensure PowerShell is Running in the Correct Mode

• If running in PowerShell Core, switch to Windows PowerShell (powershell.exe).
• Try running the command in Command Prompt (cmd) instead.

Want to supercharge your writing with AI? Let’s link Microsoft Word to Copilot in just a few steps!

First, make sure you’re signed into your Microsoft account and that Copilot is installed on your computer.

When highlighting text in Word, the Copilot popup should appear. If it doesn’t, right-click and select Copilot.

Now, you can choose between “Auto Rewrite” and “Visualize as a Table.”

If you choose “Visualize as a Table,” you will have three options: “Keep It,” “Replace,” or “Tell Copilot What You Want to Do.”

That’s it! Enjoy effortless writing with Copilot in Word.

When the default email address is disabled or inaccessible, for example the email account deactivated, server issues, password change, you may not be able to run Outlook with this error:

“Cannot start Microsoft Outlook”. Here’s a resolution using the Mail (Control Panel) option:

Here’s a clear step-by-step guide for troubleshooting and switching the default email address in Outlook:

---

How to Resolve Issues When Outlook Won’t Start and Switch to Another Default Email Address

1. Possible Reasons Outlook Can’t Start:
   • The default email address is disabled or inaccessible (e.g., account deactivated, server issues, password change).
   • Corrupted profile or data files (.pst or .ost) linked to the disabled email.
   • Add-ins or navigation pane settings causing the startup error.
2. Switch to Another Default Email Address Using Control Panel:
   • Open Control Panel by searching for it in the Windows Start menu.
   • Click on Mail (Microsoft Outlook) or Mail (32-bit).
   • Select Show Profiles.
3. Create a New Profile:
   • Under Show Profiles, click Add to create a new profile.
   • Set up a working email account in the new profile using the on-screen prompts.
   • Test the new profile to ensure functionality.
4. Set the New Profile as Default:
   • In the Mail (Control Panel) window, choose the newly created profile.
   • Check Always use this profile and click OK.
5. Remove the Problematic Account (Optional):
   • If the disabled account continues to cause issues, return to Show Profiles, select the old profile, and click Remove.