As with most things in Scrum, if it doesn't feel right then generally something isn't right.
A key principle in Scrum is responding to change and focusing on delivering real business value rather than just turning out code. The Sprint Review is critical for this process as it is the opportunity for a wider audience to provide their feedback. The team talks continuously with the Product Owner throughout the sprint, but many stakeholders don't have the time available to do this. So they love the opportunity of the Sprint Review to really engage with the team.
As a Scrum Master I emphasise to my teams that they need to go in to Sprint Reviews with the attitude of looking for feedback rather than demonstrating progress.
As an example rather than saying
"This is what we did this sprint"
I much prefer a team to say
"We added a new search function on the home page. What do you think of the positioning? There was a lot of debate in the team about whether we should pre-load it with the last search. What are your thoughts on this?"
One good trick is to use a Sprint Review rehearsal to identify possible discussion points. As a Scrum Master I would constantly interrupt a rehearsal with questions. Why did you do that? What is that for? Couldn't you have done that differently? Where there are doubts or differences of opinion I make a note and suggest that the team raises the point in the Sprint Review.
Another piece of advice is to not expect the Sprint Review to follow a rigid structure. Anticipate that there will be feedback and encourage it. If the stakeholders detect a reluctance to accept feedback they will quickly switch off. Say, for example, a stakeholder gives some feedback and a discussion starts. Let that discussion run it's natural course. Don't interrupt and say there is not enough time due to more things you want to show.
If you constantly fail to get good feedback at the Sprint Review then it is worth questioning who is attending. I have seen one practice where a team will reserve 3 chairs for customers and end-users. If these people do not attend the Sprint Review then the chairs are empty. This reminds the team that they are missing out on important feedback.