What is happening:

Initially my cursor was at "initially here". When I press Ctrl+S to save the file my cursor automatically moves to the second position.

After many tries, I've seen that it randomly moves to a point one or two lines above the place where it initially was.

alt text

(The red line is the cursor - I've drawn it manually since it wont show up in printscreen)

Did anyone notice this thing?

My version of Notepad is:

alt text

It is a problem since I keep typing and whenever I save, I have to manually bring the cursor down to the correct place or else I am typing somewhere between the lines!

  • 1
    I'm guessing there should be some images in the post but it only shows "alt text" for me. Oct 19, 2009 at 6:29
  • @T. Kaltnekar Is it fixed now?
    – Lazer
    Oct 19, 2009 at 6:32
  • Yes, images are visible now. Oct 19, 2009 at 6:40
  • Seems to be a bug, I can reproduce it. Looks like it's related to word wrapping somehow. Suggest you use notepad++ as micmcg suggested. Oct 19, 2009 at 6:57
  • 1
    From test I did - if I added a few chars and saved it didn't move. If I added enough text so it wrapped at end of line cursor moved after saving. More times it wrapped the more it moved. Oct 19, 2009 at 7:17

5 Answers 5


I noticed this problem in Windows XP Notepad. It only happens if word wrap is on when you save. The amount the cursor moves back is related to the number of new wrap points before the cursor since the last save. The more new wrap points before the cursor, the further the cursor moves back.

Why does the cursor move? When you save with word wrap on, Notepad inserts CR CR LF characters at each wrap point in the display window (but not in the saved file). The number of characters from the beginning of the display window to the cursor stays the same, but because of the extra CR CR LF characters, the cursor appears to move backward.

For more information and a step-by-step example, see Notepad bug: Saving with word wrap on inserts CR CR LF characters in the display window.

  • 1
    thanks for adding info. posts consisting primarily of a link are discouraged here to minimize future problems with broken links. Feb 17, 2010 at 4:25
  • the answer I was waiting for!
    – Lazer
    Feb 17, 2010 at 5:00
  • 1
    Actually, this bug goes all the way back to the days of Windows for Workgroups 3.11 (may go back even further). I used to use Windows Write a lot and it did the exact same thing whenever you'd save with word wrap on, though it would also change the word-wrapping slightly but not update the display, causing things to become jumbled. When Windows 95 came out, Write was renamed to Notepad and the cursor bug remained, where it remains still. In other words, this bug has existed for at least 20 years and still M$ hasn't gotten around to fixing it.
    – Kris Craig
    Oct 27, 2015 at 23:43
  • 2
    Write -- I'm pretty sure Write has nothing to do with Notepad. Windows 3.1 and 3.11 for Workgroups had both Notepad and Write, they were separate programs. The modern equivalent of Write is WordPad, not Notepad. I don't remember a bug like this in Write, but if there was one, I suspect it's not related to this Notepad bug. The Notepad bug is caused by poor use of the EM_FMTLINES message of a multi-line edit control. I think Write and WordPad use rich text controls, so I doubt it's the same thing. @KrisCraig
    – Bavi_H
    Oct 31, 2015 at 14:42
  • 2
    How long the bug has existed -- I have used versions of Notepad in Windows 3.1, 3.11 for Workgroups, 95, XP, 7, 8, 8.1, and 10. The versions from 3.1 to 95 didn't have this bug, and the versions from XP to 10 do have this bug. In this blog post, the author says he's noticed the bug in Windows 2000 and after. I guess somewhere around Windows 2000, Notepad was revised to use EM_FMTLINES, and this bug has remained ever since.
    – Bavi_H
    Oct 31, 2015 at 14:42

Regardless of whether this is a bug, if you are doing anything in notepad regularly enough for this to be an issue, you need to start using a better text editor. Try the free notepad++ for a start - http://notepad-plus.sourceforge.net/


(Can't post as a comment because I don't have enough reputation.)

According to this site, it was fixed by at least Windows 10 version 1511 (November 2015).

According to this site, the bug existed in Windows 10 on October 18 2015.

If we're going by major versions of Windows 10, the initial release was 1507, then the next major version was 1511. So by deduction, version 1511 was the first major update that had this bug fixed.



Since MS hired 166,000 employee to make sure these bugs won't be fixed for eternity, I made my own workaround for it. I use "Hot Keyboard" to fix all sort of things including this one. Make a macro like this, condition it to run only on Notepad and assign ctrl+s to it:

  1. Type some rare character like *
  2. Press ctrl+s
  3. Press home in case cursor doesn't move back
  4. Press ctrl+f , type * , enter & esc .
    Now the cursor is back where it was and you can delete that * character.
  5. Press delete

P.S, Unlike AutoHotkey, You don't need any coding with Hot Keyboard just record what you do with mouse/keyboard. When you set the speed of macro to 100X or max you won't notice any of those things happen and it seems like always when you save with ctrl+s except without that annoying moving cursor thing.

enter image description here


Open your Registry editor, and in Current User locate the following key:



  1. Create a new DWORD value called fSavePageSettings and set it to "1"
  2. if fSaveWindowPositions doesn't exist then Create DWORD and set it to "1"
  • 2
    What do these keys mean and what is their effect? Aug 15, 2012 at 16:28
  • I found a reference to these registry settings on the Microsoft Answers site, but the settings didn't fix the problem, which also occurs on Windows 7 and 8.
    – boot13
    Sep 17, 2015 at 18:12

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .