I have been running MS systems since you needed to 5-1/4' floppies to boot them. I know the difference between 32-bit and 64-bit systems. This one has me a bit frazzled.
When I run Dism.exe, I consistently get the following error:
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Error: 11
You cannot service a running 64-bit operating system with a 32-bit version of DISM.
Please use the version of DISM that corresponds to your computer's architecture.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
It's obvious that the command that's loading is the 32-bit version. I scanned the hard drive and found several versions of DISM.exe. Each time I get the same error, regardless of which DISM.exe I execute. Each time I was in an "elevated" cmd environment. I even tried going into Powershell and running it. Same problem. I have checked the path, just to be sure. sysWOW64 appears before system32 in the path variable. I have tried running dism.exe from each individual location on the drive, just to make sure the "local" command is/was being executed. Same error.
The reason for this is that sfc /scannow found some corrupted files it could not repair. I wanted to run the DISM command, then rerun the sfc command.
Where can I find the 64-bit version of dism.exe? It should be on the hard drive somewhere or at least you would think so.
I also tried running Powershell and the Repair-WindowsImage -Online -RestoreHealth. It failed with a similar error.
Outside of these commands, I will likely have to restore Windows 8.1 and start over.
What prompted all this was the laptop started doing some flaky things. For example, when you try to open a cmd environment, the system would just stall and restart explorer.exe after a few minutes. This happened repeatedly. I was finally able to get a cmd environment to open from the directory where the command is located. After that, it worked flawlessly. Similar things were happening trying to run other commands/features. This all started after installation of one of the MS security patches.
At this point, wiping the system and starting with a clean slate may be the best option.
Oh - system running Windows 8.1, latest patches. HP Laptop 750GB HD, 6GB RAM, i3 processor.
Bob