I installed v12 over v11.7, my first problem was the Procedure Entry Point error as stated by another poster here [url]Procedure Entry Point Errors After Upgrading to 12]. When I checked the About box, DOPUS was still listed as v11.7.
Last night I decided to uninstall v11 and then install v12, with a shutdown and cold start inbetween.
This has created a new problem and makes it impossible to open DOPUS.
I now get an Entry Point Not Found error, linking to a DLL. DOPUS will not open.
I am using W10:14915 Pro (fast ring preview version)
It sounds like the installer is failing to replace the Opus program files, assuming you have rebooted after installing the update. (The reboot is required. Things won't work properly if you run Opus after an update without rebooting.)
I would try uninstalling it and then deleting the program folder entirely, if anything is left.
With the non-standard install path ("F:\GPSoftware"), is that because you've diverted C:\Program Files to F:\ or has it been done in a different way?
Unless prevented, I install all my programs to "F:" (physical separate drive) and just keep Windows OS on the "C:" partition as this drive is a 240GB SSD .
I always perform a cold restart rather than a warm reboot.
I'll try uninstalling and starting again. A 'repair' install made no difference.
Problem finally solved thank you. Had trouble uninstalling as the legacy way of accessing Control Panel had stopped working along with a number of other CPL components. Using the flyout All Settings\Apps & Features to uninstall DOPUS worked.
Re-installation this morning and now all is working properly for the moment, though somehow the uninstall also prevented me temporarily of logging into Windows via the pin number option.
Apart from trying to prevent excessive writes to a my SSD drive (and the 240GB also includes a partition to run eComStation OS2), I like to separate the OS itself from programs that might corrupt the OS itself, plus some redundancy so that if the OS becomes corrupt, it is a much smaller image that needs to be restored from my images drive,, same for programs and data files, these have their own image, so I only need to spend 30 minutes restoring all my files and even better I can do that online rather than booting from a USB Linux or WinPE stick.
I also was "frightened" writing too much data on my first 1-2 SSD's, but today not anymore. They are not that expensive, 128-256 GB are cheap today (which is enough for OS, apps and a few games and data, which make use of the speed, everything else on HDD).
You should try Macrium Reflect, which recovers only changed blocks on system-restore (my 30 GB sys is restored in under 1,5 minutes).
Installing 50MB of program files to an SSD is not really going to affect the amount of data written to. It's not something worth avoiding. The write only happens once (per install/update) and is negligible compared to the terabytes of write operations over the lifetime of an SSD.
Under normal use the temp dir and pagefiles will be on an SSD and that means hundreds of MB or even a few GB are written to them every day, without them failing in everyone's machines. Another 50MB will not make any difference and isn't worth worrying about. SSDs are a lot more robust than when they first came out, too, and by the time an SSD wears out, you can get one that's 4x the size and 2x the speed for 1/2 the price.
Similarly, if a program is going to corrupt the OS, it won't make any difference whether you installed it to C:\ or F:. OS problems caused by bad apps are not something which spread through being on the same physical disk. Such problems are caused by software modifying the registry or system folders, which they can do regardless of where they are installed.
As a general point, making things non-standard is much more likely to cause problems than reduce them. (It's like registry cleaners and third-party uninstallers, as a general rule.) Even if all the software you use is written correctly, it's possible some detail will be missed when changing things. For example, if Program Files is moved and the folder permissions are wrong, it can cause things to fail. It can still make sense to have a non-standard configuration if there's a good reason for it (e.g. a very small C drive might mean you want to install programs on another drive), but doing it to reduce the chance of problems is counterproductive.
(Saying that, it does annoy me that things like GameDVR, built into Windows 10, continually write huge files to temp, with no option to divert them. Streaming everything on-screen into a video file in the temp folder can mean gigabytes of data, written over and over, and it seems wrong there is no option to divert it to a mechanical drive. But while the OS itself does things like that, worrying about the tiny write footprint of app installs is not going to make a difference. And moving temp itself to a mechanical drive is like throwing away half the benefits of an SSD in order to preserve it for longer. SSDs are there to be used, and to speed things up, not to be preserved forever.)
The first SSD was a Holy Grail, now you'll thrown with it up to 500 GB (1TB+ SSD's are still expensive, but often only needed for special usage like video-editing etc. or extraordinary games like FSX/Prepar3D )
).
)