Why no Windows 9?

Why no Windows 9?
Because 7 Ate 9.

Comments

Post a Comment

Popular posts from this blog

Error - vbe6ext.olb could not be loaded

Issue description: The target PC has both Office 2010 and 2016 installed, after uninstalled the Office 2016, and open an Excel Spreadsheet, the above error happened. Fix: Go to below folder: C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6 Rename the file "VBE6EXT.OLB" to "VBE6EXT.OLD”. Open Excel again, click Alt+F11, a popup window prompting for repairing, click "Yes". After repair completed, the problem is fixed also.
Read more

Visual Studio $(TargetDir) macro is empty

I encounter this issue in VS2017, it shall apply to older version also. To repeat the issue: 1. Create a PreBuildEvent, and type below script echo TargetDir = "$(TargetDir)" 2.  Build the project, you will see: TargetDir = "" Solution: Open the project file with a text editor, then remove the PreBuildEvent section, including the outer <PropertyGroup>. Then re-add the Pre Build Events using Visual Studio.   <PropertyGroup>     <PreBuildEvent>          <!-- Pre build commands go here -->     </PreBuildEvent>   </PropertyGroup>
Read more

LifeCycle ES4 & Word 2016 Error

LifeCycle ES4 & Word 2016 Error LifeCycle Designer ES4 does not recognize MS Word 2016 on Windows 10 While launching LifeCycle Designer ES4 and try to start from a Word doc, below error message pop up: "Word (version XP or onwards) could not be found on the machine" Problem is in Registry. LiveCycle searches only the following folders on Windows 10 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\10.0\Word\InstallRoot HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\11.0\Word\InstallRoot HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\12.0\Word\InstallRoot Create following Path in Registry: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\12.0\Word\InstallRoot create new "string value" "Path" with value "C:\Program Files (x86)\Microsoft Office\Office16\" Please remember to reboot PC for the changed registry to be effective. Reference: https://forums.adobe.com/thread/897696
Read more