• martins2

    martins2

    @martins2

    Viewing 15 replies - 1 through 15 (of 218 total)
    Author
    Replies
    • in reply to: Outlook 2016 Crashing When Closing Minimized Messages #1594063

      mlo – if it works for me and not for you, then there is some other difference. I doubt that the Windows 10 level (Pro or Home) would be significant, but you mentioned that yours is not quite up to date? I also doubt that this would be a factor, but would be worth attention. I think we are both using Office 365, and currently I have version 1702, build 7870.2024 – but this changes from time to time, so again should not be significant. But possibly yours is corrupted, in which case a Repair, or even a complete reinstall, could help. Or it could come to what other software or programs that you have running at the time – you could have something else running which causes interference? Using Task Manager or Process Explorer, you could progressively shut down other tasks and see if the problem goes away. Another possibility is your scheduled tasks: have a look in the Task Scheduler, and temporarily stop and disable anything you see in there.

      As the crash occurs when you try to close a message, it could also be something to do with the pst file. Two possibilities here: (1) some other program is also looking at it, and (2) the file is corrupted. For (1) you can use “Opened Files View” from Nirsoft; for (2) you could try the SCANPST tool, which you should have at “C:Program Files (x86)Microsoft OfficerootOffice16SCANPST.EXE”.

    • in reply to: Outlook 2016 Crashing When Closing Minimized Messages #1593835

      I don’t believe it is Classic Shell, because I also use that, plus Office 365 (with hardware graphics acceleration enabled) and Windows 10 1607, and I don’t have the problem. I can do exactly as described, and it just works as expected. My W10 is fully up to date, and is the Home version rather than Pro, but I don’t see that as significant.. Is your Classic Shell up to date? Mine is version 4.3.0.0.

    • in reply to: No Word Wrap for HTML email in Outlook 2013 #1593561

      There must be something going on at the sending end? On my PC (Outlook 2016, Windows 10), the 2017-03-14 issue displays correctly, but the 2017-03-16 issue is once again going “off the page”.

    • in reply to: No Word Wrap for HTML email in Outlook 2013 #1592894

      Same here, and the same email messages are affected. There was a thread in here on this topic – see http://windowssecrets.com/forums/showthread//170806-Outlook-2016-word-wrap-issue . There is a proposed solution there, but I could not make it work. Evidently the problem is caused by the use of non-breaking spaces in the HTML code, and the solution says to put the email into Edit mode and then replace those spaces with an ordinary space created by your keyboard. In another forum I found that a non-breaking space is made by using CTRL+SHIFT+Space; put that in the Find field, and an ordinary space in the Replace field, then do Replace All. It would find and replace many instances, but it made no difference to the email format or appearance. I would be interested to know if anyone can make this work.

      However, a somewhat less than satisfactory solution for me is simply to make the email message full-screen, by clicking the little box in the top right corner, then there is no horizontal wrapping. But then the message occupies the entire screen and you can’t see anything behind it.

      Interestingly, when I first open one of the affected emails, it appears briefly in the “normal” format, with the correct line wrapping. But then, a second or so later, it changes to the version with no line wrapping. This only happens the first time the message is opened after Outlook has started; it does not happen if the message is closed and re-opened in the same Outlook session. Perhaps there is a setting somewhere in Outlook which can control this behaviour?

    • Scanpst should only be run when Outlook is not running, and it may need to run several times to clean up all errors – but you probably knew that already.

      Another possibility is that your pst file is badly fragmented. Have you compressed it lately? If not, then with Outlook not running, go to Control Panel > Mail > Data Files. select your pst file, and click Settings > Compact Now. If the file is badly fragmented, this could take a while. It would be an idea to compress the file, then run scanpst again.

      Yet another possible cause I have seen is hardware acceleration. In Outlook, go to File > Options > Advanced, and scroll down to Display, where you can turn hardware acceleration on or off. See if resetting it makes any difference.

    • in reply to: Windows cannot find… #1590110

      Check what’s in your Path: Control Panel > System > Advanced system settings > Environment Variables > System variables > Path. The folder you are accessing may need to be defined in there.

    • in reply to: Fake Firefox Annoyance #1589222

      The way to check for genuine FF updates is from within FF. Go to Help > About Firefox, and it will tell you if it’s up to date or if there is an update available. To get an update, just click to download it, then restart FF and check again. For this to work, you need to go to Tools > Options > Advanced, and select “Check for updates but let me choose whether to install them”. You also need to be running FF as an administrator to apply an update.

    • in reply to: Outlook 2016 VBA to move email #1589221

      You could just right-click on the message and select Move. It will show a list of folders: if you don’t see the destination folder, select Other Folder; it will be remembered for next time. Or, create a rule that identifies the message and moves it. Why re-invent the wheel?

    • in reply to: Outlook 2003 stopped receiving mail #1588634

      For what it’s worth, my wife’s laptop is running Office 2003 on Windows 10, with no adverse effects. Windows updates (including the latest one) don’t affect Outlook 2003. However, it is an IPV4 machine only.

      (Same problem, adversity to change….. “I know this version of Outlook/Word/whatever, and don’t want to learn a new one”.)

    • in reply to: The past is haunting me! #1588633

      “Last week, there was a HUGE lot of them – almost 200 – which came down from the server again.”

      Are you deleting from the server as emails are received? If not, you could continue to receive the same emails over and over again. This is a per-account setting, and is found in Account Settings > More Settings > Advanced, then uncheck the box that says “Leave a copy of messages on the server”. If you have more than one email account, check that all of them are set correctly.

    • in reply to: What is the most efficient way to connect dual monitors? #1588632

      One monitor is defined as the “main display”, and obviously I know which one it is. What is puzzling me is that before I made these changes, when I had both monitors connected to the NVIDIA card, the BIOS/UEFI would display on one monitor only – the one defined as the “main display”. Now that I have both monitors connected to the Intel 4600, the BIOS/UEFI displays on both monitors, until Windows starts on the “main display” only. If that’s the way it has to be, it’s of no concern.

      Besides physically removing the NVIDIA card, I have uninstalled all the NVIDIA drivers and software. Using Revo, the uninstall found and deleted many leftover registry entries and files. So far, everything is working normally. Thanks for the assistance.

    • in reply to: What is the most efficient way to connect dual monitors? #1588438

      I had a few problems along the way. It looked good at first, but after a restart I did not see the BIOS screen where you can press DEL to enter setup. Both screens would remain completely blank until Windows started with the login screen, on the “main display” only. With a bit of fiddling around and swapping connections, I then had the opposite – the BIOS screen would appear, and it would go on to start Windows, but at the point where Windows takes over, both screens would go dark and nothing more seemed to happen. I knew that Windows had started, because of various beeps, but it was not displaying on the screens. Eventually I twigged that I had to change the initial display output, in the BIOS, from PCIe to IGFX, and to physically remove (not just disable or uninstall) the NVIDIA card. Having done all that, it seems now to be OK and the response on both screens is good. Just one minor annoyance – when I start the computer now, the initial BIOS screen appears on both monitors, and the startup stays on both screens until Windows starts with its login screen, at which point it reverts to the “main display” only. Is there a way to prevent the initial startup sequence from appearing on both screens? It doesn’t really matter, just annoying.

    • in reply to: What is the most efficient way to connect dual monitors? #1588335

      Thanks for that info. I have not seen this sort of comparison before, and don’t understand all the parameters, but it certainly looks like the 4600 is the better performer. I have connected both screens to the 4600, and have disabled (but not yet uninstalled) the GT. In the BIOS I have allocated the maximum amount of memory (1024MB) to the 4600. Both screens are running as expected, so I will run it like that for a week or so, and if it looks good I will uninstall the GT and physically remove it.

      One thing is a bit strange now though. When I look at display settings, I now see three displays. Numbers 2 and 3 are my actual screens; number 1 is a smaller box with the caption “Display not detected”. I’m guessing that this will go away if/when I finally uninstall the GT?

    • One last thought: I am the only user of my PC, so I am the only user that actually logs on. I will occasionally “run as administrator”, but the only actual logon is mine. I wonder if multiple logons by different users could have something to do with it? Maybe user A sets up his/her own defaults, but then user B logs on with no or different defaults, and somehow overwrites user A’s defaults? Could be worth experimenting with?

    • in reply to: Windows Explorer (File Manager) freezes #1587633

      That scanning is probably being triggered by the task scheduler. Open Task Scheduler, expand Task Scheduler Library > Microsoft > Windows, and look for a task called Data Integrity Scan. On mine it says “Scans fault tolerant volumes for latent corruptions”. Disable, and see if it makes a difference. If that’s not it, there could be another task on the same list; there are many other tasks that run behind the scenes.

    Viewing 15 replies - 1 through 15 (of 218 total)