Install Works 8 on Windows 10 64 bit

I would like to ask some help in my issue: I tried to install Works 8 on Windows 10 64 bit operation system, but the setup process failed all the time, because the installer wants to install Internet Explorer 6 to my machine, but it doesn’t work (the system is 64 bit, the IE 6 installer is 32 bit). Please, help me in this case, because Works 8 is my father’s most used software, and he don’t want to change it to Office (it’s totally different for him).

I tried to install in any compatibility mode, but it doesn’t work.

Much thanks in advance!

Replies (6) 

Is there an option to customize setup and uncheck IE? Could you try downloading version 9 to see if it skips installing version?

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I have works 9.0 installed on my 64 bit Windows 10.

You will have to try to find an installer for Works 9 and then see if it will allow you to use the Work 8 key to activate it.

Your other option is to use a «VM», virtual machine, tool. In it you would install an older version of Windows than can run Works 8. Here are some articles about this idea

VIRTUALIZATION — VM — VIRTUALBOX
http://www.heidoc.net/joomla/technology-science.
One might still own old software or games that aren’t supported on recent versions of Microsoft Windows, so a virtual machine could be the solution to get them running anyway. Although Virtual PC is officially only for professional or business editions of Windows, it can be installed on home editions without any problems.

INSTALL AND TEST OPERATING SYSTEMS VIRTUALLY IN WINDOWS USING HYPER-V
http://www.askvg.com/tip-install-and-test-opera.
Posted: 19 Oct 2015 07:34 AM PDT
Whenever a new operating system (whether its a new Windows version or a new Linux distro or a new iOS version) is released or is being developed and tested, many people want to try its new features and user interface changes. To test the new operating system, you must first need to install it in […]

Hyper-V is «free» part of Windows Pro, which is a $100 upgrade from Windows Home.

****
Join the crowd
.
Be unique

Will work on 64bit windows

1,836	уникальных посетителей
30	добавили в избранное

First you need to download Crysis Warhead Fix.zip that contains the necessary file for this fix.

The file is 118MB in size so it shouldn’t take long to download.

NOTE: If you don’t trust the files linked for download in this guide, you can do the same thing by dodownloading the game from GOG and after installing copy Bin64 folder to steam folder.
Rename Bin64 to Bin32. Then inside newly renamed Bin32 delete Crysis.exe and rename Crysis64.exe to Crysis.exe and thats it.

Now that you have downloaded the zip we can truly begin.
Inside Crysis Warhead Fix.zip you want to locate and open Installs folder.

Inside you will find 3 programs: directx_Jun2010_redist, vcredist_x64 and vcredist_x86.
You want to install all 3.

After that you want to open your steam Crysis Warhead folder.
Go to your steam library and right click on Crysis Warhead,
a little menu will show up and in it sellect Properties.

A new window will open and in it you want to click on LOCAL FILES tab

then inside that menu you want to click BROWSE LOCAL FILES.

That will open the install folder of Crysis Warhead.
Next you want to locate Bin32 and Bin64 folders and delete them.

Lastly you want to copy Bin32 folder from the Crysis Warhead Fix.zip to the Crisys Warhead folder.

Now you can run the game. Steam overlay should also be working.

Will 32-Bit Office 2010 work on a new 64-bit machine?

I am currently running Office 2010 on an older Windows 7 32-bit laptop.

Will my current install CDs for Office 2010 install and run on a newer Windows 10 64-bit machine?

Thanks in advance.

Replies (2) 

Power to the Developer!

MSI GV72 — 17.3″, i7-8750H (Hex Core), 32GB DDR4, 4GB GeForce GTX 1050 Ti, 256GB NVMe M2, 2TB HDD

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Yes it certainly will. I am using that exact mix right now.

Although it was not tested on Win 10 when it was released, Office 2010 does work on Win 10

Actually, MS STILL defaults to installing 32 bit Office even on 64 bit Windows. Mostly as a hold over from original release of 64bit Office because then, and still now to a lesser extent, many addon makers did not bother making 64 bit version of their tools (no market). That included MS!

****
Join the crowd
.
Be unique

The world needs more ‘neeks’.

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

CreateThread() fails on 64 bit Windows, works on 32 bit Windows. Why?

Operating System: Windows XP 64 bit, SP2.

I have an unusual problem. I am porting some code from 32 bit to 64 bit. The 32 bit code works just fine. But when I call CreateThread() for the 64 bit version the call fails. I have three places where this fails. 2 call CreateThread(). 1 calls beginthreadex() which calls CreateThread().

All three calls fail with error code 0x3E6, «Invalid access to memory location».

The problem is all the input parameters are correct.

All three calls to CreateThread() are made from a DLL I’ve injected into the target program at the start of the program execution (this is before the program has got to the start of main()/WinMain()). If I call CreateThread() from the target program (same params) via say a menu, it works. Same parameters etc. Bizarre.

If I pass NULL instead of &threadID, it still fails.

If I pass NULL as myParam, it still fails.

I’m not calling CreateThread from inside DllMain(), so that isn’t the problem. I’m confused and searching on Google etc hasn’t shown any relevant answers.

If anyone has seen this before or has any ideas, please let me know.

Thanks for reading.

ANSWER

Short answer: Stack Frames on x64 need to be 16 byte aligned.

Longer answer: After much banging my head against the debugger wall and posting responses to the various suggestions (all of which helped in someway, prodding me to try new directions) I started exploring what-ifs about what was on the stack prior to calling CreateThread(). This proved to be a red-herring but it did lead to the solution.

Adding extra data to the stack changes the stack frame alignment. Sooner or later one of the tests gets you to 16 byte stack frame alignment. At that point the code worked. So I retraced my steps and started putting NULL data onto the stack rather than what I thought was the correct values (I had been pushing return addresses to fake up a call frame). It still worked — so the data isn’t important, it must be the actual stack addresses.

I quickly realised it was 16 byte alignment for the stack. Previously I was only aware of 8 byte alignment for data. This microsoft document explains all the alignment requirements.

If the stackframe is not 16 byte aligned on x64 the compiler may put large (8 byte or more) data on the wrong alignment boundaries when it pushes data onto the stack.

Hence the problem I faced — the hooking code was called with a stack that was not aligned on a 16 byte boundary.

Quick summary of alignment requirements, expressed as size : alignment

Anything larger than 8 bytes is aligned on the next power of 2 boundary.

I think Microsoft’s error code is a bit misleading. The initial STATUS_DATATYPE_MISALIGNMENT could be expressed as a STATUS_STACK_MISALIGNMENT which would be more helpful. But then turning STATUS_DATATYPE_MISALIGNMENT into ERROR_NOACCESS — that actually disguises and misleads as to what the problem is. Very unhelpful.

Thank you to everyone that posted suggestions. Even if I disagreed with the suggestions, they prompted me to test in a wide variety of directions (including the ones I disagreed with).

Written a more detailed description of the problem of datatype misalignment here: 64 bit porting gotcha #1! x64 Datatype misalignment.

NI Product Compatibility for Microsoft Windows 10

Overview

Contents

Moving Existing Applications to Windows 10

In general, existing Windows 7 and Windows 8 applications should continue to function in Windows 10, but hardware drivers and development environments may need to be updated to the August 2015 release or newer.

Accessing NI Software in Windows 10

Windows 10 reintroduces the Start menu, which changes how you access NI products. Top-level shortcuts, such as MAX, are listed under the alphabetized N section of the All Apps menu. All secondary shortcuts are under the NI section of the menu.

As with Windows 8, NI software will not operate as a Windows Store app and any application created with NI software will not be able to operate as a Windows Store app. This is because the operating system limits necessary access to the Win32 API.

Known Compatibility Issues

Silverlight Support

Some NI components require Microsoft Silverlight to function properly. The default browser in Windows 10, Microsoft Edge, does not support Silverlight. Google Chrome also no longer supports Silverlight. Windows 10 includes Internet Explorer 11 for backward compatibility, which supports Silverlight. All Silverlight pages launched from MAX will use Internet Explorer, but Silverlight-based pages launched manually using a default browser that does not support Silverlight, such as Edge or Chrome, will fail to open. For more information about using Silverlight-based pages on Windows 10, refer to KnowledgeBase Remote Front Panels, NI Network Browser, and the Web Interface (WIF) Do Not Work in Google Chrome Version 42 or Higher

Fast Startup Issues

NI strongly encourages its customers to disable fast startup. For more information, refer to KnowledgeBase Hardware Not Detected or Not Functional in Windows Due to Fast Startup.

Repairing NI Software After Upgrading

Performing a repair on NI software after upgrading to Windows 10 can result in a loss of access to hardware associated with repaired drivers. To restore the NI device drivers to a working state, perform a second repair on the affected device drivers. This was an issue originally discovered when upgrading from Windows 8.0 to 8.1 that also applies to Windows 10 upgrades.

How to Use the Windows 10 Compatibility Tables

• In the table below, the column titled ‘Windows 10 64-bit (Using 32-bit Software)’ indicates the first version of 32-bit software that will run within the Windows on Windows (WOW64) emulation layer.
• In the tables below, Not supported means the end user cannot use 32-bit NI software in their 64-bit software scenarios. Not applicable means the software bitness for that version of the operating system does not exist or is not a valid configuration. For example, MAX or LabWindows™/CVI™ development environments do not have 64-bit versions of the executable, but will work on 64-bit Windows 10. A 64-bit program will not work on a 32-bit operating system.

NI Product Compatibility for Microsoft Windows 10

What is the difference between Windows 10 32-bit and Windows 10 64-bit?

Windows 10 32-bit can run on either x86 or x64 hardware. Similar to Windows XP 32-bit, Windows 10 32-bit provides access only to 32-bit addresses. As a result, even though Windows 10 32-bit will run on x64 hardware, it is limited to using 4 gigabytes of RAM. Windows 10 32-bit cannot run 64-bit versions of drivers or software designed to run natively on 64-bit operating systems.

Windows 10 64-bit can be installed only on x64 hardware. This version of the operating system allows software to use 64-bit addresses to access hardware and can therefore access much larger memory spaces. In order to run successfully on Windows 10 64-bit, all drivers must have native 64-bit support. However, most 32-bit software applications can run within a Windows 10 64-bit emulation layer.

For more detailed information on the difference between Windows 32-bit and 64-bit, see Using NI Products on 32-bit and 64-bit Windows.

Software

Because Windows 10 release date was very close to NI August 2015 software release date, August 2015 releases were not documented with respect to Windows 10 support. Based on testing after Windows 10 release, the following NI software packages are compatible with the listed versions of Windows 10 32-bit and Windows 10 64-bit. As of 2016, all new versions and service pack updates of NI software document their compatibility with Windows 10 in their Readme files. If there is any question about the compatibility of a piece of software with the 64-bit versions of Windows and LabVIEW, please refer to the Readme for that release.

NI Software	Windows 10 32-bit	Windows 10 64-bit	Windows 10 64-bit
		(Using 32-bit Software)	(Using 64-bit Software)

GPIB-Serial Converter Software	19.0	Not applicable	19.0
InsightCM Server	Not supported	Not supported	Not supported
LabVIEW Communications System Design Software	Not applicable	Not applicable	2.0
LabVIEW Communications System Design Suite	Not applicable	Not applicable	2.1
LabVIEW NXG	Not applicable	Not applicable	1.0
NI Analog Video Generator	Not supported	Not supported	Not supported
NI Analog Waveform Editor	Not supported	Not supported	Not supported
NI AudioMASTER	Not supported	Not supported	Not supported
NI Calibration Executive	3.6 — 5.0	3.6	6.0
NI DIAdem	2015 SP1	2015 SP1	2015 SP1
NI Digital Video Generator	Not supported	Not supported	Not supported
NI Digital Waveform Editor	3.0	3.0	Not applicable
NI FlexLogger	Not applicable	Not applicable	2018 R2
NI Functional Safety Editor	Not supported	Not supported	Sep-17
NI I/O Trace	15.0	15.0	15.0
NI InstrumentStudio	Not applicable	Not applicable	2018
NI LabVIEW 32-bit	2015 SP1	2015 SP1	Not applicable
NI LabVIEW 64-bit	Not applicable	Not applicable	2015 SP1
NI LabVIEW for LEGO® MINDSTORMS	2016	2016	Not applicable
NI LabWindows/CVI Run-Time Engine	2015	2015	2015
NI LabWindows™/CVI™	2015	2015	Not applicable
NI Lookout (Lookout FDS)	Not supported	Not supported	Not applicable
NI MATRIXx	7.2.8	7.2.8	7.2.8
NI Measurement & Automation Explorer (MAX)	15.0	15.0	Not applicable
NI Measurement Studio	2015	2015	2015
NI Multisim	14.0.1	14.0.1	Not supported
NI Package Builder	19.0	19.0	19.0
NI Package Manager	19.0	19.0	17.0
NI Picture Quality Analysis (PQA)	Not supported	Not supported	Not supported
NI Real-Time Hypervisor	Not supported	Not supported	Not supported
NI Requirements Gateway	2014	2014	Not applicable
NI SignalExpress	Not applicable	Not applicable	Not applicable
NI Switch Executive	2017	2017	2017
NI SystemLink Client	Not applicable	Not applicable	17.0
NI SystemLink Server	Not applicable	Not applicable	17.0
NI TestStand	2014 SP1	2014 SP1	2014 SP1
NI Ultiboard	14.0.1	14.0.1	Not supported
NI Update Service	2.3	2.3	17.0
NI VeriStand	2015 — 2018 SP1	2015 — 2018 SP1	2019
NI Video Measurement Suite (VMS)	Not supported	Not supported	Not supported
NI VirtualBench	16.0	16.0	16.0
NI Vision Builder for Automated Inspection	2015	2015	2015

Add-Ons and Toolkits

The following NI Add-ons and Toolkits are compatible with the listed versions Windows 10 32-bit and Windows 10 64-bit:

NI Software	Windows 10 32-bit	Windows 10 64-bit	Windows 10 64-bit
		(Using 32-bit Software)	(Using 64-bit Software)

FlexLogger Plugin Development Kit	Not applicable	Not applicable	1.0
NI Automotive Diagnostic Command Set	15.0	15.0	15.0
NI Bluetooth Toolkit (Run-Time, Generation, Analysis)	15.0	15.0	15.0
NI Combustion Analysis System	2015	2015	Not supported
NI ECU Measurement and Calibration Toolkit	15.0	15.0	15.0
NI FM/RDS Measurement Suite	1.0	Not Supported	Not supported
NI GNSS Simulation Toolkit	3.0	Not Supported	Not supported
NI InsightCM SDK	2.0	2.0	Not supported
NI LabVIEW Advanced Signal Processing Toolkit	15.0 3	15.0 3	2018
NI LabVIEW Analytics and Machine Learning Toolkit	2017	2017	2018
NI LabVIEW Application Builder	2015 SP1	2015 SP1	2015 SP1
NI LabVIEW C Generator	2015 3	2015 3	Not applicable
NI LabVIEW Communications MIMO Application Framework	Not supported	Not supported	Not supported
NI LabVIEW Control Design and Simulation Module	2015 3	2015 3	2016
NI LabVIEW Database Connectivity Toolkit	2015 3	2015 3	2019
NI LabVIEW DataFinder Toolkit	2016	2016	Not supported
NI LabVIEW Datalogging and Supervisory Control Module	2015 3	2015 3	Not applicable
NI LabVIEW Desktop Execution Trace Toolkit	2015 3	2015 3	2016
NI LabVIEW Digital Filter Design Toolkit	2015 3	2015 3	2018
NI LabVIEW Electrical Power Toolkit	2016	2016	Not applicable
NI LabVIEW Embedded for ARM Module	Not supported	Not supported	Not supported
NI LabVIEW FPGA Module 1	2017	2017	2018
NI LabVIEW FPGA Xilinx ISE 1	Not supported	Not supported	Not applicable
NI LabVIEW FPGA Xilinx Vivado 1	Not applicable	2018	2018
NI LabVIEW MathScript RT Module	2015 3	2015 3	2016
NI LabVIEW Mobile Module	Not applicable	Not applicable	Not applicable
NI LabVIEW Module for LEGO MINDSTORM	Not applicable	Not applicable	Not applicable
NI LabVIEW myRIO Toolkit	2015 3	2015 3	Not applicable
NI LabVIEW OPC UA Toolkit	2017	2017	2018
NI LabVIEW PID and Fuzzy Logic Toolkit 2	2015 SP1	2015 SP1	2015 SP1
NI LabVIEW Real-Time Module	2015 SP1	2015 SP1	Not applicable
NI LabVIEW Report Generation Toolkit for Microsoft Office	2015 3	2015 3	2015 3
NI LabVIEW roboRIO Toolkit	2015 3	2015 3	Not applicable
NI LabVIEW Robotics Module	2015 3	2015 3	Not applicable
NI LabVIEW Softmotion Module	2015 3	2015 3	Not applicable
NI LabVIEW Statechart Module	2015 3	2015 3	Not applicable
NI LabVIEW Touch Panel Module	Not supported	Not supported	Not applicable
NI LabVIEW Unit Test Framework Toolkit	2015 3	2015 3	2016
NI LabVIEW VI Analyzer Toolkit	2015 3	2015 3	2016
NI LabVIEW Wireless Sensor Network (WSN) Module	2015 3	2015 3	Not applicable
NI LabWindows/CVI Execution Profiler Toolkit	1.0	1.0	1.0
NI LabWindows/CVI PID Control Toolkit	2.1	2.1	Not applicable
NI LabWindows/CVI Real-Time Module	2015	2015	Not applicable
NI LabWindows/CVI Signal Processing Toolkit	7.0.2	7.0.2	Not applicable
NI LabWindows/CVI SQL Toolkit	2.3	2.3	2.3
NI License Manager	3.7	3.7	3.7
NI Modulation Toolkit	15.0	15.0	15.0
NI Motion Assistant	Not supported	Not supported	Not applicable
NI OPC Servers	2016	2016	Not supported
NI-RFFastACP	1.0.0	1.0.0	1.0.0
NI-RFmx	1.2	1.2	1.2
NI-RFPM	Not supported	16.0.0	16.0.0
NI Software Calibration Management Toolkit for LabVIEW	2015	2015	Not supported
NI Sound and Vibration Measurement Suite	15.0	15.0	15.0 (excluding configuration of Express VIs)
NI Spectral Measurements Toolkit	15.0	15.0	15.0
NI SystemLink Server — Test Module	Not applicable	Not applicable	18.0
NI TDMS	15.0	15.0	15.0
NI TestStand ATML Toolkit	2013	2013	2017
NI Vision Development Module	2015 SP1	2015 SP1	2015 SP1
NI-VRTS	Not applicable	1.5	1.5
NI WLAN Toolkit	15.0	15.0	15.0
RFIC Test Software	Not supported	3.0	3.0
Semiconductor Device Control Add-On for InstrumentStudio	Not applicable	Not applicable	2019
VCSEL I-V Test Software	Not supported	Not supported	20.0

1 The LabVIEW FPGA Module is partially supported on Windows 10. However, the Xilinx tools used for your NI FPGA device might not be. For details, refer to LabVIEW FPGA Module Compatibility with Windows 10.

2 NI LabVIEW PID and Fuzzy Logic Toolkit was included with base LabVIEW beginning with LabVIEW 2014.

3 This software version only supports Windows 10 when used with LabVIEW 2015 SP1.

Hardware Drivers

The following NI Hardware Drivers are compatible with the listed versions of Windows 10 32-bit and Windows 10 64-bit.