Announcement

Collapse
No announcement yet.

Microsoft updates sabotaged my program

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Microsoft updates sabotaged my program

    The code created by PBCC v6.03 that was working this morning on my Windows 7 computers was
    Code:
    1030 GRAPHIC PRINT SYM;" now appears in groups  ";
         SHELL (MyApp$,1)
         SHELL (ENVIRON$("COMSPEC") + " /C findstr "+SYM+" c:\stocks\mynotes\groups\*.txt >stuffy")
         SFN="stuffy":IFN=FREEFILE:OPEN SFN FOR INPUT AS IFN
    1060 IF EOF(IFN) THEN CLOSE IFN:GRAPHIC PRINT:KILL "stuffy":GOTO 1080
         INPUT #IFN,SLI:SLI=RIGHT$(SLI,-25)
    After today's FIVE Windows Updates labelled as "important", that program is NOT WORKING ANYMORE and three of the malicious "updates" are stated to be NOT UNINSTALLABLE. Specifically, I tried to uninstall KB4512506 and KB4474419 and found that didn't solve the sabotaged operaations. They were also immediately reoffered as "important updates". The three that were declared incapable of being uninstalled were KB890830 Malicious Software Removal along with two versions of KB915597 numbered 1.299.2006.0 for the first one which didn't seem to have caused problems this morning and 1.999.1765.0 which was part of the four "updates" this afternoon after which my program was sabotaged.
    That same code still works as of *this* moment on my Windows 10 machine if only because Microsoft might not have gotten around to inflicting those "updates" yet and I haven't allowed that machine to be subjected to the crime infested whirled wide wubb.
    Does anybody have any notion of how I can correct for this apparent sabotage by the convicted criminal predatory monopoly other than over writing the current computer from my FULL SYSTEM BACKUP updated with the nightly IMPORTANT FILE BACKUPS that I have available? Has anybody even heard of such problems being inflicted on owners of Windows 7 computers?



  • #2
    Wow that is a REALLY negative post, I can understand frustration but Microsoft is "not out to get you" . To be fair and honest, I will say that MOST times its is the programmer's implementation that is the problem, not Windows. Sometimes a major security flaw and subsequent update may require you to do something in a different way, but that is very rare unless you are doing something very dicey security-wise to begin with.

    What you posted is not NEARLY enough to help explain what may be going on. Heck, you are not even telling us the actual failure. Only thing I can see is you are interacting in a directory in the root ("C:\Stocks") which is NOT a smart idea, You should have stopped using that sort of concept when you upgraded from Windows 95/98/ME (even then it was frowned upon). Windows XP was lax, Vista and beyond got more forceful, and for VERY good and secure reasons. You should be writing only to directories the logged in user has rights (i.e somewhere in the user profile or in the shared profile). You may not agree with what I am saying but that is what sound programming is expected to follow.
    <b>George W. Bleck</b>
    <img src='http://www.blecktech.com/myemail.gif'>

    Comment


    • #3
      The experience that I'm undergoing is an extemely unpleasant experience. The directory structure under Windows 10 has been revised so that c:\stocks is no longer where the operation is conducted on Windows 10 but still is on Windows 7. It is now down in my "user" directory. HOWEVER, I discovered moments ago that what *was* working this morning on Windows 10 is *also* not working this evening so I can only suspect that one of my brief ventures onto the Internet allowed the modifications to be made to my Windows 10 computer too. You suppose that there are any "clients" involved in my operations "allowed to access based on UAC". There are no such things. I am the solitary person ever allowed to access anything on any of my computers with the only exception being the invasive "convicted criminal predatory Microsoft monopoly" as determined by the judge in their trial. Sorry but that phrase is from a Washington DC *judge* and provides judicial notice as to the nature of the company.
      As far as how I know *where* the problem is located, in the COMSPEC coding that was working, I inserted several test codings immediately after the COMSPEC line and its immediately following line which directed the program to tell me whether and of what size the "stuffy" file had been created. None of those test codings was ever executed. Instead, immediately after the COMSPEC was supposed to have created the "stuffy" file, the program was wrongfully REDIRECTED back to an entirely different part of the program and instead of being allowed to preserve the file that was apparently never created or to see the information from that file in relation to the
      Code:
       GRAPHIC PRINT SYM;" now appears in groups ";
      the entire execution was sent flying off to an entirely different aspect of the code. That is my problem and now appears to be adversely impacting both operating systems. Likely others of my programs where the COMSPEC structure is used although I have yet to test any of those other programs.

      Comment


      • #4
        What's the error message? what line does it occur on?
        Do you "runas administrator" for your application?
        Are you logged in as an ordinary user or as administrator?

        Comment


        • #5
          What anti-virus program are you using?

          Comment


          • #6
            There is no "error message". Code execution is simply REDIRECTED from the area shown in what I posted to an entirely different part of the code. In a solitary environment such as mine, there is no usefulness to requiring any of my programs to be "run as administrator". That comes up only when the slopperating system prevents me from carrying out normal and useful activities without redefining myself from "sole and separate operator" to "administrator" which I also am. There is only one login status provided at this time which is me as me.

            Comment


            • #7
              > the entire execution was sent flying off to an entirely different aspect of the code.

              ???
              Something else has to be wrong. No way is a Windows update going to change the logical flow of a compiled program.

              Comment


              • #8
                Microsoft is helping us, DESPITE what we want to do. We should NEVER run anything as administrator unless we specifically need to (i.e. a specific admin function) even if we are the ONLY user. The sooner this is understood as not only being BEST PRACTICES but as ONLY PRACTICES the sooner real securtiy starts taking place; take this from a career digital security professional

                Every, and I mean EVERY, excuse people try to use to perpetuate a "need" to follow the old way and how BAD Microsoft is for preventing us from doing it just reinforces why malicious programmers (malware) take full advantage of that and why it works SO well.

                It's a shame some horses are so "against drinking", cause its good healthy water.
                <b>George W. Bleck</b>
                <img src='http://www.blecktech.com/myemail.gif'>

                Comment


                • #9
                  Yes I understand the delight of hackers for having tons of snippets of malicious code to refer to in constructing their attacks which is what so called "anti-virus programs" provide. On the Windows 7 machine the only thing in that direction is Spybot which Windows 10 refused to allow me to install there insisting that I rely on *their* anti virus operations. My fallback position each time I am effectively attacked is the (1) over write with last known full system backup, (2) update with most recent nightly backup of all typically modified files, and (3) proceed to get back to work on what matters to me. The problem here seems to be that I have been effectively attacked by the five Microsoft Updates which I allowed on their pretense that these were "important updates". Important enough to destroy the functionality of an essential program of mine, which was working perfectly before their 'updates", is not *important* at all to anybody but *them* as part of their invasive control demands..

                  Comment


                  • #10
                    Yes George, as I said, I never use "administrator" unless Windows 10 compels me to do so to accomplish what needs to get done. As for "compilable example" Stuart, the entire program depends on its 36 Megabytes size on disk of *files*. None of it can be tested or reviewed outside the code section which results in REDIRECTION.

                    Comment


                    • #11
                      Start adding COPIOUS log file code (or use ztrace) to record changes to help pinpoint where potential failures could occur.

                      When you say redirection... what is being redirected? i.e. reading/writing from wrong drive path? jumps to wrong point in your code (ex. Something like you push button "A" and button "B" code executes)? You are not very clear in your explanation of the failure.

                      Sorry if I opened up negative but your initial tone makes Microsoft out to be the cause and I'll bet you a shiny nickle its your code somewhere

                      BTW you really NEED to take off the tin foil hat. Dead serious. Patches are not some conspiracy most happen for very good reasons (even Telemetry has SOME merits). I know I won't change your mind but if I can change at least ONE person's then it is one person less added to a botnet. You are a stock professional, you understand stocks but you sure are not a security professional, I am a security professional so trust what I say.
                      <b>George W. Bleck</b>
                      <img src='http://www.blecktech.com/myemail.gif'>

                      Comment


                      • #12
                        Bob,
                        Would that going off to a different part of the program be related to this:
                        Code:
                         
                        GOTO 1080
                        I would think that if a redirection was serious then it would crash the program or even worse cause a BSOD.

                        Also, you'll likely want to validate the file exists before you try to open it.

                        I received these updates today with no problems to report:
                        KB4512506
                        KB890830 (MSRT)

                        I didn't receive the other 2 you mentioned.
                        My system is Windows 10 1903.

                        Comment


                        • #13
                          Originally posted by Bob Grumbine View Post
                          As far as how I know *where* the problem is located, in the COMSPEC coding that was working, I inserted several test codings immediately after the COMSPEC line and its immediately following line which directed the program to tell me whether and of what size the "stuffy" file had been created. None of those test codings was ever executed.
                          How do you know it is not the
                          SHELL (MyApp$,1)

                          causing your problem?

                          Comment


                          • #14
                            Progress report on my analysis of the now defective program: Using an alternative physical machine, I RESTORED my system as it existed at the close of business on Friday August 9. On that restored system, my program works as designed and as it always had until today. Supporting the views of those who think it is NOT the Microsoft "updates" is the fact that three other programs of mine which use the COMSPEC language within their local executions show no signs of trouble. I have not been able to test the other two programs that use the COMSPEC language because they are dependent on timely downloads of new information to run at all. In addition, I ran Spybot and MalWarBytes on the impacted primary computer and neither one of them could find anything whatever wrong with the computer. This one program MYNOTES happens to be the most important aspect of what I do because it organizes access to roughly Six Thousand files so that I can call them up when I want to see what information I have gathered about those six thousand entities and to classify or reclassify them as indicated by the "now appears in groups" language just before the REDIRECT occurs. My program also happens to be sufficiently controversial with some argumentative participants in a professional web site that I visit regularly that a sufficiently competent hacker working from *that* location when I'm there "maybe coulda" specifically attacked *that* program to put it out of operation. Only another suspect at the moment beyond Microsoft "updates" and the fact that three other COMSPEC using programs show no sign of being impacted. But now having proof that the problem is no older than five days (during which time I have made no changes whatever of my own to the program itself which was last compiled by me on May 9) has me exploring how to regenerate the former alternate physical computer into a fully functional active computer.

                            Comment


                            • #15
                              Originally posted by Bob Grumbine View Post
                              After today's FIVE Windows Updates labelled as "important", that program is NOT WORKING ANYMORE and three of the malicious "updates" are stated to be NOT UNINSTALLABLE. Specifically, I tried to uninstall KB4512506 and KB4474419 and found that didn't solve the sabotaged operaations. They were also immediately reoffered as "important updates". The three that were declared incapable of being uninstalled were KB890830 Malicious Software Removal along with two versions of KB915597 numbered 1.299.2006.0 for the first one which didn't seem to have caused problems this morning and 1.999.1765.0 which was part of the four "updates" this afternoon after which my program was sabotaged.
                              Further information on the problem. I copied the known working version of my program from the RESTORED alternate physical computer on which everything is as of last Friday August 9 and its related .bas file onto an SD card. Then I replaced the now inoperable equivalents on my Windows 7 and Windows 10 current computers with those known working versions. What this says to me is that the ENVIRONMENTS on my computers have been changed in the past five days and that the alternate suspect isn't one because the program is precisely as it was when it was working last Friday (and yesterday although that hasn't been proved by subsequent replication).. The program is not where the problem is despite my quoting the section of code *where* the redirect occurs. The program is fine as designed and written. It is the environment that has been adversely altered and the only known suspect for that (especially in light of Spybot and MalWareBytes being unable to find anything wrong on the Windows 7 computer) is the convicted criminal predatory Microsoft monopoly with its NO WAY TO UNINSTALL "updates". I'm back to my original question: "Does anybody have any notion of how I can correct for this apparent sabotage by the convicted criminal predatory monopoly other than over writing the current Windows 7 computer from my FULL SYSTEM BACKUP updated with the nightly IMPORTANT FILE BACKUPS that I have available?" It gets more complicated with the Windows 10 computer because I have done two more days of installations that haven't been protected with full system backups.

                              Comment


                              • #16
                                Oh boy, you really dare to claim that an update broke your program while in the very few lines you posted something like
                                Code:
                                SHELL (ENVIRON$("COMSPEC") + " /C findstr "+SYM+" c:\stocks\mynotes\groups\*.txt >stuffy")
                                is shown, which is a big No Go since at least Windows NT4.

                                is the convicted criminal predatory Microsoft monopoly with its NO WAY TO UNINSTALL "updates".
                                Actually it's people like you that drove MS to this decision, as too many "smart guys" out there thought and still think they know better than the ones who created the OS and insist in doing all kinds of not-so-clever shenanigans, opening the door for malware on their machines, which in turn utilize the resources of said machine to execute their malicious payload (e.g. DDoS) onto others.

                                As a corporate sysadmin, I'm sick and tired of lazy programmers who forces crucial security measures to be disabled in order for their programs to work properly.

                                Comment


                                • #17
                                  George

                                  [Off topic]
                                  Re your post #11's link to 'ztrace Helper'. I also love Patrice Terriers's zTrace and have used it quite a few times in Callback functions to watch certain aspects without disturbing the flow. I missed your Helper during my leave of absence when a certain individual was still being allowed to post. Your use of the #UTILITY metastatement, to remove logging completely with a single constant change, is a cracking idea - in some cases I have spent sometime commenting zTrace lines. Thank you. [/Off topic]

                                  Comment


                                  • #18
                                    Me a not so cool pa. "Shame on me" for suspecting the judicially noticed convicted criminal predatory Microsoft monopoly of having anything but the "best interests" of its monopolized "customers" at heart. Yes, I found a trivial bug in the original Windows 7 version of my program which was "forgiven" by Windows 7 other than for flying off the handle as it did. So I inserted some error catching code to properly handle my decrepit old man's occasional fumble fingered entries. Then I figured that perhaps I should start over on the Windows 10 version so I copied the new .bas file over as a replacement for Win10s equivalent and went through it with all of the major modifications required to make a Windows 7 developed program run properly on a Windows 10 computer. Bingo! the program is now back to working on Windows 10 and I'm in the midst of the essential full system backup to protect my last several days of installations. THIS PROBLEM HAS BEEN SOLVED and I do thank those who tried to help.

                                    Comment


                                    • #19
                                      George Bleck As a security professional I'm sure you understand how the Capital One, Apple Cloud, Sony, Equifax, the early days hacking of two of the biggest banks' credit card files, and the plethora of other real world "demonstrations" were accomplished. As for "trust" it's something which a stock and bond professional understands only in terms of scammers demanding that we *trust them* with our money for them to play with and dissipate. For that matter for whirled wide wubb scammers demanding we *trust them" to "protect" us from such as the Automated Clearing House, Electronic Funds Transfers, Point of Sale Terminals, and "Check21" forgery facilitating systems imposed by the Frauderal Reserve Bored, none of which have any validation from the *owner* of the funds stolen but only the "sayso" of the felony thieves. So don't be too upset if the meaning of trust is not in my working vocabulary. I'm only a decrepit old man wary of repeating all of the harsh learning experiences I've been through. This time, yes, a mistake of my own which compounded on the new Windows 10 physical computer.

                                      Comment


                                      • #20
                                        Originally posted by Bob Grumbine View Post
                                        Me a not so cool pa. "Shame on me" for suspecting the judicially noticed convicted criminal predatory Microsoft monopoly of having anything but the "best interests" of its monopolized "customers" at heart. Yes, I found a trivial bug in the original Windows 7 version of my program which was "forgiven" by Windows 7 other than for flying off the handle as it did. So I inserted some error catching code to properly handle my decrepit old man's occasional fumble fingered entries. Then I figured that perhaps I should start over on the Windows 10 version so I copied the new .bas file over as a replacement for Win10s equivalent and went through it with all of the major modifications required to make a Windows 7 developed program run properly on a Windows 10 computer. Bingo! the program is now back to working on Windows 10 and I'm in the midst of the essential full system backup to protect my last several days of installations. THIS PROBLEM HAS BEEN SOLVED and I do thank those who tried to help.
                                        IOW: Nothing to do with the company you so scurilously excoriated. Clearly the bug was not trivial. It was just your bad programming that was previously tolerated by the OS until additional security was implemented to handle programmers like you who expose your and other peoples systems to security threats.

                                        Comment

                                        Working...
                                        X