Please read what actively happened. They pressured Netscape devs to stop working on the browser. They prevented OEMs from bundling other things than their software, they also made it intentionally difficult for Sun Java code to be modified/changed (it wasn't just Netscape, Sun was involved in it too).
Here is a link if you need a refresher. A lot more complicated than "WAAAA Microsoft has a popular OS and bundled browser so they got in trouble!!!!" -
https://www.justice.gov/atr/us-v-microsoft-courts-findings-fact#iva
Some highlights.
Microsoft's first response to the threat posed by Navigator was an
effort to persuade Netscape to structure its business such that the company would not distribute platform- level browsing software for Windows.
Decision-makers at Microsoft worried that simply developing its own attractive browser product, pricing it at zero, and promoting it vigorously would not divert enough browser usage from Navigator to neutralize it as a platform. They believed that a comparable browser product offered at no charge would still not be compelling enough to consumers to detract substantially from Navigator's existing share of browser usage. This belief was due, at least in part, to the fact that Navigator already enjoyed a very large installed base and had become nearly synonymous with the Web in the public's consciousness. If Microsoft was going to raise Internet Explorer's share of browser usage and lower Navigator's share, executives at Microsoft believed they
needed to constrict Netscape's access to the distribution channels that led most efficiently to browser usage.
Microsoft easily could have implemented Sun's native method along with its own in its developer tools and its JVM, thereby allowing Java developers to choose between speed and portability; however, it elected instead to implement only the Microsoft methods. The result was that if a Java developer used the Sun method for making native calls, his application would not run on Microsoft's version of the Windows JVM, and if he used Microsoft's native methods, his application would not run on any JVM other than Microsoft's version. Far from being the unintended consequence of an attempt to help Java developers more easily develop high- performing applications, incompatibility was the intended result of Microsoft's efforts. In fact, Microsoft would subsequently threaten to use the same tactic against Apple's QuickTime.
Microsoft continued to refuse to implement Sun's native method until November 1998, when a court ordered it to do so. It then took Microsoft only a few weeks to implement Sun's native method in its developer tools and JVM.
