I’m yet to check this one out. Reblogging to avoid losing the link among the ocean of bookmarks those I already have.
We are using Oracle applications R12 12.0.6 with JDK 6.0 while most of the clients are using JRE 7/8 based on different business requirements (With full knowledge that there would be unexpected results due to the compiled versions). We’ve observed a peculiar issue with the JRE applet once after the upgrade to Windows 10 version 1803. The Java applet started showing too small fonts while launched from displays with high DPI resolutions.
Digging in brought me to the following discussion:
Although there are multiple recommendations, for EBS environment, Please follow the below instructions:
Launch the JAVA applet by opening a forms based module.
Open task manager and locate “Java(TM) Platform…”, right click and open properties. This will open the properties for “jp2launcher.exe”. Click on “Compatibility” and click on “Change high DPI settings”. Now check “Override high DPI scaling behavior. Scaling performed by:” to “Application”. Refer the image for more details.
Once the changes are made to the properties of the executable, restart the box. It could be specific case, the changes were not applied until a restart for me.
Although it fixes the font scaling issues, the toolbar area of the Oracle forms are remains scaled with pretty small icons. I am yet to find out a fix for this minor annoyance. May be quite soon.
Windows 10 gets more interesting day after day. I feel like Microsoft is slowly helping my HUGE beasty desktop machines to start looking like a MOBILE PHONE, well enough said.
One of the latest issues with Windows 10 version 1803 (build: 17134.81) is, one cannot add the .NET Framework 3.5 feature using “Turn Windows features…”, the attempts start reporting you are not connected to internet, which is not true (Microsoft should grow up)
So if you are looking for a quick solution to the said, don’t worry, Microsoft has truly messed up documentations available here:
& you should read this one as well
Or if you don’t want to get confused, follow the instructions below:
Using the Windows Media Creation Tool for Version 1803, create ISO and mount it
Browse to sources\sxs folder within the ISO that’s been already mounted. Example, my ISO file is mounted on J: drive, hence the path to sources files is “J:\sources\sxs”
Copy the path and with an administrator account, open “LOCAL” group policy editor
Click Computer Configuration, click Administrative Templates, click System, and then double-click the Specify settings for optional component installation and component repair setting.
and once the LOCAL policies are updated, you have to apply it. Apply the policy changes using “gpupdate /force”. Don’t worry about domain policies (if you are using a domain joined computer)
Now try to install “.NET Framework 3.5”, should complete without giving more errors.
Hope this helps few out there