อัปเดตครั้งล่าสุดเมื่อ
22 พ.ค. 2025
Learn how to fix AVX2-related Error 195 during InDesign, InCopy, or InDesign Server installation by ensuring system compatibility.
Error 195 during inDesign server Installation
When installing InDesign, InCopy, or InDesign Server, you may encounter Error 195 indicating that the system configuration does not meet the requirements. This error is often related to AVX2 support.
Identify the problem
- Error Code: During installation, you may see Error 195. This error suggests that the system configuration isn't compatible.
- Install Log: Check the installation log for detailed error messages. Look for entries related to system prerequisites and compatibility issues.
Check compatibility with AVX2 support
- Verify CPU Compatibility:
- Ensure your CPU supports the AVX2 instruction set. You can check this by referring to the CPU's datasheet or using tools like CPU-Z or HWiNFO64.
- For Intel CPUs, AVX2 support requires Haswell or newer processors.
- Check ESXi Version and VM Hardware Version:
- AVX2 requires ESXi 6.0+ and VM hardware version 11+.
- Confirm that your host server is running ESXi 8.0 U2 and the VM hardware version is 21, which meets the requirements.
- BIOS Settings:
- Ensure that AVX2 is enabled in the BIOS. Access the BIOS settings during startup (usually by pressing keys like F2, F12, DEL, or ESC) and navigate to the CPU configuration section.
- Verify that AVX2 is enabled under the CPU or Advanced settings.
Resolve Installation errors
- Reboot and BIOS Check:
- If AVX2 is enabled in the BIOS, but the error persists, perform a reboot to ensure the settings are applied correctly.
- Double-check with the hardware manufacturer (e.g., Dell) for compatibility and settings.
- Update ESXi and VM Hardware:
- Ensure that your ESXi version and VM hardware version are up-to-date. Sometimes, updates can resolve compatibility issues.
- Review Installation Components:
- Check if the installer includes components like Media Encoder or Bridge that might not be compatible with the server's specifications. Creating a new build without these components might resolve the issue.