Windows update and progam not working anymore.

Hi,
So I was running this program perfectly fine yesterday, windows did an update on shutdown.
Now the program not working anymore.
I see the program pop up in the task manager for 2 seconds, then gets "Suspended" and vanish.

The same old story, I've replaced half my software because of this windows 10 moody situation where it pick some exe that has been working fine and decide that it doesn't like it anymore and won't run it the next boot.

Getting sick of having to find an alternate software every time.

Anyone can enlighten me with a solution?

I removed all the updates and did system restore way before the update.
Messed with compatibility setting, still not running.

Funny thing, I have an older ver of the program and it ran fine just now.

Solution:
From windows setting > Update & security > Windows security > App & browser control
Then scroll all the way down to > Exploit protection setting
Set DEP to off.
Restart.

Hi, the extent to which you seem to be experiencing this doesn't seem at all typical AFAIK.

Could you
a. state what Windows build you are using?
Windows key + R, winver

b. state what the last update was?
(See your Update History)

c. Identify the problem program, its version and where you got it from if possible.

d. Similarly list a couple of others you have found no longer working.

I have a LOT of progs installed from over 2 years ago (build 10240 on) - there's only one I for which I have to wait for an upgrade per build, and that's entirely appropriate in the case of that program.

Thanks.

Hi, it is possible that old programs become incompatible, as you know.

Some older programs will work if you
a. install them in compatibilty mode
b. run them in compatibility mode

(rt click, Troubleshoot compatibility) I think you're aware of this.

Unfortunately I don't have build 1803- I've decided to skip it, first because 1 GUI modifying prog takes about 3 months before it's compatible, second 'cos 1803 had so many issues reported, third by that time it wasn't long before the next is due (!).

However you say you experienced this problem with Win 10 builds before 1803.

I do have a copy of Imtoo video convertor v 6.8, which runs perfectly.

Nero is updated annually, and Nero 8 is many years out of date. It can include a lot of drivers, so does not at all surprised me you'd need an update.

CD/DVD Label Software anc Cover Maker | Disc Labeler 7 | SureThing.Com
- v 7 (2016) - unfortunately you have not quoted version numbers in general as asked.

I'll assume you have v6. This installs and runs on my 1709 ok.

I suggest you try

a. Basics - check your disk and file system

1. First check your disk:
Download and run Hard Disk Sentinel (trial)
Post a screenshot of its GUI using the Insert Image icon above your post.
If all disks are reported as good, continue.

2. Now check your file system:

From an admin command or powershell prompt
[Windows key + X, click command prompt (admin)]
chkdsk C: /F
Your PC will need to restart.
Post back the result, which you can get after a restart as follows:
Read Chkdsk Log in Event Viewer in Windows 10 | Windows 10 Tutorials
or
How to read Event Viewer log for Chkdsk in Windows 10 [Tip] | dotTech

b. If ok from an admin command prompt run
SFC /SCANNOW

c. If ok try a clean boot, then see if your problem programs still crash.

d. Explore your Reliability History
(type Reli in your Cortana search box)

Click on related red x's looking for a report of the program crash.

(You could use Appcrashview (free) which makes finding these rather easy).

Drive
Reason I suggested the drive check was to see if this might suggest a basic reason for erratic behaviour.
It could be linked if drive defects cause programs to be corrupted and crash, but perhaps your programs aren't installed to that disk, in which case it's a separate matter.

Good thing your failing drive isn't your system disk- hope you have a backup.

Note: there are a number of (free) programs you can run that monitor drive health and can generate alerts at an early stage.
Using disk imaging routinely (strongly recommended here) is also a useful check on drive integrity (the used space at least) as problems reading the disk will be detected as CRC errors. Put another way, once your drive has started failing, you probably can't create an image.

Emulator
Sega Genesis emulators | Emulation General Wiki | FANDOM powered by Wikia

- not sure which yours is- might be there's a version 2.14- or is it the one that's 1.1 - you have 0.0.9.61
You'd be in a better position to check that.

A BEX error is a “Buffer Overflow Exception”. This error is typically raised when Microsoft Windows detects that a programs tries to put more data than possible in a region of memory.
- DEP - data exception prevention - you can set exceptions to this to hide such problems, but not really recommended.

black said:

Didn't want to get in to much details because as said, I either found an alternate or upgrade.
I've updated my Nero to 10 and CD/DVD labeler to 6, Ver 5 stopped for no reason.
I hate getting a new software when there is nothing wrong with it just because I was forced to upgrade windows and that windows is so picky, not to mention I've to learn using them all over again.
Waste of time and money.

Anyway.
Following your suggestions:
A. Checked and found error with windows drive, picture attached.

Not sure about this, but I don't think this error has anything to do with programs not running as I suffered from this issue way back, before having this error.
But hey thanks to you we discovered an error in the drive lol.


2. This was tricky, but I managed to copy the log from the Powershell, hope it's right.

Code:

TimeCreated : 9/16/2018 9:38:20 PM
Message     :
              Checking file system on C:
              The type of the file system is NTFS.
              Volume label is Windows.

              A disk check has been scheduled.
              Windows will now check the disk.
              Stage 1: Examining basic file system structure ...
                521472 file records processed.
              File verification completed.
                9786 large file records processed.
                0 bad file records processed.

              Stage 2: Examining file name linkage ...
                10777 reparse records processed.
                632710 index entries processed.
              Index verification completed.
                0 unindexed files scanned.
                0 unindexed files recovered to lost and found.
                10777 reparse records processed.

              Stage 3: Examining security descriptors ...
              Cleaning up 9782 unused index entries from index $SII of file 0x9.
              Cleaning up 9782 unused index entries from index $SDH of file 0x9.
              Cleaning up 9782 unused security descriptors.
              CHKDSK is compacting the security descriptor stream
              Security descriptor verification completed.
                55620 data files processed.
              CHKDSK is verifying Usn Journal...
                36212296 USN bytes processed.
              Usn Journal verification completed.
              Correcting errors in the Volume Bitmap.
              Windows has made corrections to the file system.
              No further action is required.
               511420415 KB total disk space.
               174640876 KB in 312767 files.
                  207536 KB in 55623 indexes.
                       4 KB in bad sectors.
                  644179 KB in use by the system.
                   65536 KB occupied by the log file.
               335927820 KB available on disk.
                    4096 bytes in each allocation unit.
               127855103 total allocation units on disk.
                83981955 allocation units available on disk.
              Internal Info:
              00 f5 07 00 b5 9e 05 00 50 c3 0a 00 00 00 00 00  ........P.......
              94 02 00 00 85 27 00 00 00 00 00 00 00 00 00 00  .....'..........
              Windows has finished checking your disk.
              Please wait while your computer restarts.

B. Already did sfc /scannow
C. Already tried that.
D. Ran the program and found the report about it. picture attached.

HDDs don't usually go bad at once, it's likely it had problems for long time but you didn't notice right away, so those SW problems may have started a while back because of it. Doesn't has to be system disk or even have those programs installed to it to cause troubles system wide.

If your programs aren't installed on that drive and don't make use of data on that drive, they shouldn't be affected by it directly. However bad drives can affect your system when you don't expect it.

Best deal with it or simply remove or disconnect it for now.

black said:

So how can we be sure? Will installing the program on different HD should make it run?
Or it won't work because the Windows drive/files could corrupt as whole?

Only files on bad disk get corrupted but windows keeps on reading or attempting to read all drives and bad parts can interfere by slowing down ind interrupting operation. That causes problems to whole system. In cases like that it's better to backup what you can from damaged drive and remove it or replace it.
On any HDD, a file if large enough, can be spread over several blocks/sectors not necessarily next to each other and if one of those sectors/blocks is damaged by even one bit or byte, whole file is useless and system may be looking for it fruitlessly. Examples of system looking thru all disks are de-fragmentation and indexing for instance.
All together, "One bad apple.......", you know the rest.